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

Annotations already cover read-only, idempotent, non-destructive semantics, and the description adds genuinely new behavior: results are ordered highest first, and an unfiltered call is refused, which warns the agent away from a guaranteed error. It does not discuss result limits, pagination, or what the refusal looks like, so it stops short of full behavioral coverage.

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?

Three tight sentences: what it does, why you'd use it, then the constraint and the fallback. The critical scoping rule and the alternative are front-loaded with no filler.

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?

An output schema exists, so return values needn't be explained, and the description covers purpose, ordering, refusal behavior, and the correct alternative. The only gap is not spelling out the category-versus-entity_name relationship given that both parameters are optional in the schema.

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 baseline is 3, but the description adds real semantics: ranking is scoped to exactly one named group, and despite zero required parameters an unfiltered call will be rejected, effectively mandating a category or supplier filter. Minor residual ambiguity about whether category and entity_name can be combined, and the word 'supplier' versus the schema's 'entity_name'.

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 and resource plus scope: ranking the open task's lines within one named category or supplier by revenue or units, highest first. It is immediately distinguishable from the sibling twelfth_list_products, which it explicitly names as the different tool.

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?

Gives an explicit use case (compare rate of sale within a group), an explicit exclusion (it refuses an unfiltered ranking), and an explicit alternative with the exact sort key to use instead (twelfth_list_products sorted by units_l4w). Nothing about tool selection is left to inference.

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