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

Annotations already declare readOnly/idempotent/closed-world, and the description adds real value beyond them: returns provenanced records, unverified specs are never inferred, and products missing the sort value sort last. It does not disclose pagination or result-size limits, but the ordering and provenance guarantees are meaningful disclosure.

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?

Front-loaded with the query patterns, then descending/sort semantics in a compact single paragraph with an inline example. Dense but every clause carries information; slightly long for one sentence-stack but 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?

No output schema exists, and the description compensates by describing the return (provenanced product records) and tie/edge handling (missing sort values last). Adequate for a 5-param filtered-rank tool; would reach 5 with a note on result limits or tie-breaking among equal sort values.

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; the description earns above that by defining 'priceUsd' as the price of record each product's page prints and by giving a worked example of a spec-key sort (sortBy:'battery_mah' descending:true). Minor gaps: no constraint semantics on brand matching (exact vs partial).

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 chain (filters by maxPriceUsd/brand, then ranks by a field) on a specific resource (products in a category), opening with the two canonical query shapes it answers. An agent can distinguish it from search_products or find_best without opening a schema.

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?

The opening 'For "best <category> under $N" and "which <category> has the most <spec>"' gives concrete when-to-use conditions. It stops short of naming an alternative (e.g. search_products, find_best) or stating when NOT to use it, so no explicit sibling routing.

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