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

With annotations already covering the safety profile (readOnly, idempotent, non-destructive), the description still adds substantial behavioral context: linked owner wallets are excluded, ranking stops before a 50% asking-price jump, prices are unverified, and gas is excluded. These algorithmic and data-provenance invariants are exactly what an agent needs and cannot get from structured fields.

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 dense sentences with no filler; the ranking rule is front-loaded and the caveats are packed into the tail. Every clause carries information.

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 structure need not be explained, and the ranking/caveat text is strong. However, the required 'budget' parameter and pagination parameters are left semantically opaque, and the core 'AB[500]' concept is never defined, leaving gaps for an agent with no prior context.

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 only 25% — just the 'profile' parameter is documented — so the description carries the burden but explains none of budget, limit, or offset semantics (e.g., whether budget is total or per-item, or the currency/units). The phrase 'each row is a budget alternative' hints at per-row budgeting, but that is too faint to compensate for the coverage gap.

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 object ('Rank indexed AB[500] asks by ETH per added percentage point of edition ownership'), which clearly separates it from sibling tools like compare_project_prices or search_projects. It loses a point because 'AB[500]' and 'edition ownership' remain domain jargon that an unfamiliar agent cannot decode from the text alone.

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 closing clause 'each row is a budget alternative, not a basket' gives useful interpretive guidance on how to consume results, but the description never states when to pick this tool over siblings such as compare_project_prices, nor any prerequisites or exclusions for the call itself.

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