Corner radius as a design decision
Radius carries tone. Square corners read as technical and dense — tables, code, dashboards. A small radius of 4 to 8px reads as neutral and modern. Large radii of 16px and up read as friendly and consumer-facing. Fully rounded ends (a radius at or above half the height) read as a pill, which is why tags and filter chips use them.
The one rule worth holding to is consistency: pick two or three values, use them everywhere, and make nested elements use a smaller radius than their container. A nested box with the same radius as its parent looks wrong because their curves run parallel at different offsets — the optical rule is that the inner radius should be roughly the outer radius minus the padding.
px versus %
Pixel radii stay fixed however the element is sized, which is what you want for cards and buttons. Percentage radii are computed against the element's own width and height, so 50% always yields an ellipse whatever the dimensions — useful for avatars and dots, confusing anywhere else, since resizing the box silently changes the curve.
Per-corner control
Unlinking the corners covers the cases a single value cannot: a speech bubble with one square corner, tabs rounded only at the top, or a grouped button bar where the first and last elements round outward and the middle ones stay flat. The generated shorthand lists the corners clockwise from the top left, which is the order CSS expects.