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

With no annotations provided, the description carries the full burden. It discloses that the operation is on-chain, involves no custody/signing/moving, and runs at the current block. Critically, it discloses a significant behavioral trait: a maker may gate the position on an access licence token, and roughly four in five such positions will return a clear reason instead of a price, explicitly framing that as a strategy property rather than an error. This is exceptional transparency beyond basic read-only.

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 sentences total: the first front-loads the core purpose and read-only guarantee; the second gives a concrete use case; the third adds an important behavioral caveat. No wasted words, every sentence earns its place. The structure is clear and efficient.

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 the tool's moderate complexity (4 params, no output schema), the description covers purpose, usage, and critical behavioral notes. It does not describe the return format or exact response structure, which would be helpful since there is no output schema. However, the description gives enough to understand what to expect (output amount, possible reason instead of price). The missing response shape is a minor gap, so a 4 is appropriate.

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 75%, with descriptions for hash, chain, amount, and direction. The description itself adds no additional parameter details beyond what the schema already provides. It does not mention amount units or direction semantics, but the schema covers those. Baseline of 3 is appropriate since the description does not compensate for the 25% gap (chain default) but the schema already has reasonable descriptions.

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 clearly states the verb 'Price' a stablecoin swap against one position, with on-chain and current block qualifiers. It distinguishes from siblings by focusing on quoting a single position, whereas siblings handle positions, stats, chains, badges. The 'no custody, nothing signed, nothing moved' phrase reinforces its read-only nature.

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?

Explicitly instructs to use this tool 'to check USDC/USDT liquidity and get the output amount before preparing a swap.' This provides a clear use case. It does not name alternative tools or exclusions, but given sibling names and context, the intended usage is unambiguous. The note about access licensing provides important context on when a price might not be returned.

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