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

Annotations already cover the read-only and non-destructive profile, so the bar is lower. The description still adds genuinely useful operational context beyond the annotations: a rate limit of 5/min, a 1,000-per-page size, and the underlying endpoint. It stops short of describing the response shape or what 'named attributes' look like.

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?

A single dense sentence that front-loads the resource and packs pagination, throttling, and endpoint with no filler. Every clause earns its place.

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, the description still gives the pagination model and rate limit an agent needs to call it safely. It would be fully complete with a brief note on the return shape or how to iterate pages beyond the schema's next.page hint.

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 coverage is 100%, so the parameters are fully documented in the schema, including how to use next.page and next.skip. The description adds only the '1,000 per page' sizing hint, which the schema partially restates. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific verb+resource ('List product classifications and their named attributes'), which is clearly distinct from sibling list tools like skuvault_list_brands or skuvault_list_products. It doesn't explicitly name a contrast sibling, but the resource is unambiguous.

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?

Usage is implied by the resource - an agent would infer this is for enumerating classification taxonomy. However, there is no explicit when-to-use guidance, no mention of prerequisites, and no routing to or from alternatives such as skuvault_list_products.

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