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

Beyond the annotations, it discloses crucial operational behaviors: the return of a quote envelope, the expiration mechanism (unix ms format), and the fixed expiration window (180 seconds). This provides high-value context for execution.

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 highly efficient. It front-loads the purpose, clearly defines the behavioral trade-offs of the modes, and concludes with output metadata, with no wasted words.

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 complexity of a multi-mode financial quoting tool, the description is complete. It covers input constraints (mode-specific logic), output format (envelope), and output lifecycle (expiration time).

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 description adds valuable semantic information, specifically that the amounts are 'base-unit integer strings' and specifies that slippage requirements are tied to the 'auto' mode. This compensates for the 29% coverage gap in 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 purpose is 'Quote repaying debt.' It effectively distinguishes itself from sibling tools by explaining the mechanism of debt repayment ('auto' vs 'manual').

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?

It provides explicit guidance on how to use the 'auto' mode (via flash-loan swap and requires slippage) versus the 'manual' mode. This tells the agent exactly which scenario the tool is designed for.

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