get_clob_swap_quote

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

With no annotations provided, the description carries the full burden. It does mention that the amount is in human-readable units and will be converted, which is a useful behavioral detail. However, it does not explicitly state that this is a read-only operation or that it does not execute the swap, leaving some behavioral ambiguity.

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 concise sentences, front-loaded with the primary purpose and followed by a critical usage detail. There is no fluff or repetitive information, making it highly 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?

For a simple quote tool with no output schema or annotations, the description covers the essential information: what it does, the key output (exchange rate), and an important input format detail. It is sufficiently complete for an agent to use correctly, though it could mention whether fees or other quote details are included.

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?

The schema already provides full descriptions for all four parameters (100% coverage). The description's note about human-readable units is helpful but redundant as it duplicates the schema's own parameter description. Thus, the description adds minimal value beyond the schema.

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 tool's function with a specific verb ('get') and resource ('swap quote from the CLOB exchange'). It also distinguishes itself from sibling tools by explicitly mentioning 'CLOB', which differentiates it from generic swap quote tools.

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 implies this tool is for obtaining a quote on the CLOB exchange, which provides some context for its use. However, it does not explicitly compare itself with alternatives like get_swap_quote or explain when to choose one over the other, so the guidance is only implied.

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