broker_quote_swap

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

No annotations provided, so description carries full burden. States it creates a proforma quote and requires confirmation, but does not disclose side effects like fund reservation, rate limits, or outcome if unconfirmed. Adequate but not thorough.

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, front-loaded with 'STEP 1', and every sentence is informative. 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 no output schema and no annotations, description adequately explains the tool's role as a provisional quote step. Could mention expected output (e.g., quote ID) but provides sufficient context for a stepwise workflow.

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 covers 100% of parameters with descriptions. Description adds value by hinting to use wallet_get_pockets for IDs, which aids parameter selection beyond 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?

Description clearly states 'Swap/exchange one cryptocurrency for another between pockets' with a specific verb and resource. It distinguishes from siblings like broker_quote_buy/sell and broker_confirm_quote by specifying it's a proforma quote and step 1.

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 positions as 'STEP 1', states requirement of subsequent confirmation with broker_confirm_quote, and advises using wallet_get_pockets to find pocket IDs. Provides clear when-to-use and next-step guidance.

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