base: baseSwapQuote

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adding 'Get current USD price and swap quote' confirms it is a read-only query. It also warns about volatility, which aligns with the openWorldHint. No contradictions found.

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?

Two sentences: first states purpose, second provides a critical usage note and a concrete address hint. Every sentence is essential, no fluff. Front-loaded with the core action.

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 simplicity (3 parameters, no output schema, clear annotations), the description is sufficient. It explains what is returned (USD price and swap quote) and gives a key pointer for native ETH. Missing structural info about quote format but not critical for selection.

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 100%, so the schema already documents all parameters. The description adds value by specifying 'Use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE for native ETH,' which clarifies the token address for ETH, a common special case. This exceeds the baseline of 3.

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?

Clearly states 'Get current USD price and swap quote for Base tokens.' It specifies the action (get), the resource (swap quote and price), and the blockchain (Base). This distinguishes it from sibling swap quote tools for other chains like ethSwapQuote or bscSwapQuote.

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 description includes a strong usage guideline: 'ALWAYS fetch fresh prices - crypto is volatile.' This tells the agent to always request a new quote rather than caching. It also provides the address for native ETH, which is a practical hint. However, it does not explicitly state when not to use this tool or name alternatives.

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