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

No annotations are provided, so the description must carry the behavioral burden. It implies a read-only quote by saying 'ETH out', but never explicitly states that this does not execute a trade, how the quote is derived, or whether it reflects current curve state.

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 sentence with no wasted clauses, but the phrasing 'ETH out' is awkward and front-loads an ambiguous output concept rather than the action. It is concise but not as clear as it could be.

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?

For a quote tool with no output schema and no annotations, the description should clarify that it returns an ETH estimate and that it is non-mutating. Those essentials are missing, leaving the agent to infer the core contract.

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 0%, so the description must compensate. It adds that 'amount' is a whole-token amount and that the token can be v1 or v2, but it leaves the string format for token and amount (address? id? decimals?) completely unexplained.

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 phrase 'ETH out for selling a whole-token amount on the curve' implies a sell-quote operation, and the token/amount context is clear. However, it never explicitly says it returns a quote, and the v1/v2 parenthetical is cryptic; an agent has to infer the purpose from the tool name more than from the description.

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?

No guidance on when to use this versus quote_buy, build_sell_tx, or agentpad_buy. It doesn't state prerequisites such as token validity, curve state, or whether this is a dry-run quote versus an executable action.

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