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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial detail beyond them: sales-size ladder, 1%/2%/5% thresholds, limiting factors such as cost versus visible order-book end, and across_venues conditions. It discloses how the metrics are computed and what historical windows are covered.

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?

The content is mostly useful and front-loads the core idea, but it is delivered as one dense, hard-to-parse paragraph with nested clauses. A structured list of returned metrics would be clearer without losing 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?

There is no output schema, so the description carries the burden of explaining return values, and it enumerates the key metrics, thresholds, historical scope, and amount_usd behavior. It does not specify the exact response shape, but it is complete enough for an agent to understand what the tool returns.

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 100%, so the schema already explains symbol and amount_usd. The description adds that amount_usd prices that exact sale now on every venue as quote() would, but otherwise adds little parameter meaning beyond the schema.

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 states that this tool computes what selling a token for dollars (USDCx) nets as a share of value, including ladders, thresholds, and historical worst shares. It also distinguishes the amount_usd path from quote(), but the purpose is embedded in a dense noun phrase rather than stated as a direct verb-plus-resource definition.

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?

It implies usage for lending, vault, and risk tools needing collateral exit value, and notes that amount_usd mirrors quote(). However, it does not explicitly say when to choose this over quote or market_overview, nor when not to use it.

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