pons_quote_sell

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

No annotations are provided, so the description carries the full transparency burden. It discloses the calculation approach, fees-on-output handling, state-diff overrides, the eth_call cross-check, and the quote result fields. It doesn't explicitly state 'no transaction is executed', but 'eth_call' and 'quote' strongly imply read-only behavior.

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 description is a single dense sentence with no filler. Every clause adds value: the operation, the math model, the on-chain cross-check, and the returned fields.

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?

Given there is no output schema, the description helpfully names the return values and the cross-check result. It gives a solid mental model for a quote tool, though it stops short of defining the meaning or units of each returned field or explicitly stating that no trade is executed.

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 baseline is 3. The description adds useful context around fees and output fields, but it doesn't elaborate on how tokenAmount or seller map into the quoted result beyond what the schema already states.

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 opens with a specific verb and resource, 'Quote a bonding-curve sell', immediately distinguishing it from buy/swap siblings. It also specifies the mechanism: local exact curve math cross-checked against an on-chain eth_call of sell().

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 use case is clear: quote a sell on a bonding curve. However, it never explicitly says when to prefer this over pons_quote_buy or pons_quote_swap, nor does it mention any exclusions or prerequisites.

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