spraay_bridge_quote

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

Discloses cost ($0.005 USDC), which is critical behavior beyond annotations. Annotations show readOnlyHint=false, but description clarifies it's a paid quote. Could add more about validity period or execution guarantees.

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, front-loaded with main purpose. No wasted words. Efficient and clear.

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?

Description covers cost, supported chains, and return info (estimated output, fees, execution time). Output schema exists so return details are complete. Could mention if quote is valid for limited 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?

Schema has 100% coverage with descriptions. Description adds no extra parameter details beyond listing supported chains, which is already in schema descriptions. Baseline 3 for high schema coverage.

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?

Description clearly states it gets a cross-chain bridge quote via LI.FI aggregator, listing many supported chains. Differentiates from siblings like spraay_bridge_chains (chains list) and spraay_swap_quote (single-chain swap).

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 states when to use (getting a cross-chain quote) and implicit context from siblings. Does not explicitly exclude single-chain swaps or alternatives, but purpose is clear enough.

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