Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish this is a safe, closed-world read (readOnlyHint=true, openWorldHint=false). Beyond that, the description usefully discloses the shape of the payload (rule categories plus their locking rationale) and a precedence rule relative to a brief, but says nothing about behavior on a missing/invalid id or what form the rules come back in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the payload contents lead. The phrase 'the sentences that lock them' is evocative but underspecified rather than verbose, so the terseness costs clarity without saving much length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameter documentation, the description is the only source of return-shape information, and it only gestures at the payload ('rules ... and the sentences that lock them') without structure. For a lookup tool in a dense family of get_* siblings, it leaves the agent guessing about the id format and the response layout.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single 'id' parameter is an undocumented bare string. The description never clarifies whether the id is a family name, slug, or generated identifier, so it fails to compensate for the coverage gap despite the parameter being required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates what a family contains (radius, button style, density, shadow, plus the rationale sentences), which implies a retrieval of that record, but it never states the verb or that it returns a family by id. It also gives no signal distinguishing it from siblings like get_theme, get_recipe, or get_piece that presumably return related design artifacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no routing to any of the 17 sibling tools. The precedence statement ('the family wins over a brief') is about downstream conflict resolution, not about when an agent should call this tool rather than get_theme or get_recipe.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.