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

The annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds genuinely new context beyond them: auth requirement (wallet login), a consent gate (recovery-policy acknowledgement), irreversibility risk ('a successful burn cannot be reversed by Vino'), and cost allocation ('customer pays gas on both chains') plus the absence of signing/broadcast. Mild tension with readOnlyHint=false exists since a quote reads as passive, but the operation_id/recovery-policy parameters suggest persisted state, so this is clarification rather than contradiction.

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?

Four short sentences, front-loaded with the purpose before prerequisites and caveats, with essentially no filler. Slightly terse jargon ('CCTP Standard', the entity 'Vino') and an abrupt fragment ('No signing or broadcast') keep it from being a 5, but it is efficient overall.

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 6-parameter, fully-required tool with 0% schema description coverage and no output schema, the description leaves critical calling information missing: chain ID format, atomic amount units, recipient format, the role of operation_id, and what the returned quote actually contains (fees, limits, expiry). It conveys behavioral context well but not enough to invoke the tool correctly.

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% across 6 required parameters, so the description carries the full burden and mostly does not meet it. It does hint at accept_recovery_policy (via 'recovery-policy acknowledgement') and destination-related concepts ('destination mint'), but source_chain, destination_chain, recipient, amount_atomic (atomic units), and operation_id are entirely undefined in both the schema and the description.

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 names a specific verb and resource: 'Quote a capped CCTP Standard USDC route', plus the constraining qualifiers ('capped', 'CCTP Standard'). An agent can tell this is a pricing/quote operation rather than an execution step, but the description never names the obvious sibling (cross_chain_transfer_step) that presumably performs the actual transfer, so differentiation must be inferred.

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?

Prerequisites are stated explicitly ('Requires wallet login and explicit recovery-policy acknowledgement'), and 'finish the same destination mint' implies this is a precursor to a transfer step. However, there is no explicit when-to-use versus cross_chain_transfer_step or the other cross-chain siblings, and no stated condition under which an agent should skip this tool.

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