q402_oft_quote

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

No annotations are present, so the description carries the burden; it discloses the operation is read-only with no auth and describes the return values (native messaging fee and delivered amount). It does not cover error conditions or rate limits, but this is sufficient for a quote tool.

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?

Three sentences: purpose, return, and alternative/read-only. Front-loaded with the core function, no filler.

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?

Without an output schema, the description appropriately states the return information. It covers the token, chain set, and read-only nature, leaving little ambiguity for selection and invocation.

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% with descriptive parameter text for src/dst/amount, so the description need not add parameter detail; it doesn't. The description doesn't delve into parameter semantics beyond the schema, so baseline 3 applies.

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?

States the tool quotes LayerZero fees for USDT/USDT0 bridging across the OFT set, a specific verb+resource. It clearly distinguishes itself from sibling q402_bridge_quote for USDC.

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?

Explicitly directs USDC users to q402_bridge_quote instead, and the description implies use for USDT OFT quotes. Also notes read-only and no auth, providing context for when it's appropriate.

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