Polygon: polygonSwapQuote

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

Discloses the underlying swap providers ('Uses Uniswap X or 0x'), adding value beyond the annotations which already indicate read-only, non-destructive, and idempotent behavior. The native MATIC address hint further aids understanding.

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?

Extremely concise with two sentences. First sentence states the core purpose, second provides a critical detail. No extraneous text, perfectly front-loaded.

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?

No output schema is provided, and the description does not describe the return format (e.g., price, estimated gas, slippage). For a swap quote tool, this is a meaningful gap, though annotations partially compensate by indicating read-only behavior.

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 descriptions cover all parameters with good clarity. The description enhances understanding by specifying the address for native MATIC, which is not in the schema. This adds meaningful context beyond what the schema provides.

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 'Get swap quote for Polygon tokens', specifying the verb and resource. The mention of 'Polygon' differentiates from other chain-specific swap quote tools, but does not explicitly distinguish from siblings like bscSwapQuote or ethSwapQuote beyond the chain name.

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?

Provides a practical hint for native MATIC address but lacks explicit guidance on when to use this tool versus alternatives. No when-not-to-use or exclusion conditions are mentioned.

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