usdc_get_convert_quote

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by stating that the quote keeps a gas reserve, which is non-obvious and directly affects how an agent should interpret or use the quote.

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 two tightly written sentences with no filler. The core purpose and gas-reserve behavior are front-loaded, and the amount semantics are stated briefly.

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 read-only quote tool with fully documented parameters and annotations, the description covers the essential purpose and gas-reserve behavior. However, with no output schema, it does not explain what the quote returns or how it should be used before execution, and it lacks guidance on when to choose it over sibling quote or conversion tools.

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 documents all parameters including amount, chainId, accountRef, and session details. The description repeats the amount semantics ('raw native or "max"') but adds little beyond what the schema provides, so the baseline 3 is appropriate.

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 uses a specific verb and resource: it quotes converting the chain's native gas token to USDC. It clearly implies a read-only quote rather than execution, which helps distinguish it from siblings like usdc_convert_native, but it does not explicitly name or contrast those alternatives.

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?

Usage is only implied by the word 'Quote' and the reference to a gas reserve. There is no explicit guidance on when to use this instead of usdc_convert_native, usdc_get_trade_quote, or usdc_buy_with_native, and no stated exclusions.

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