create_trade

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

No annotations provided, so description carries full burden. It discloses expiration (15 seconds) and agreement requirement, but lacks post-conditions (e.g., what happens after booking: trade state, confirmation). This moderate disclosure earns a 3.

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?

Two sentences front-load the main action, with no wasted words. Every sentence serves a purpose: defining action and providing critical constraint (expiration + alternative).

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 tool's simplicity (two params, no output schema), the description covers preconditions and constraints well. It lacks details on return values or trade confirmation, but overall it's suitably complete for the complexity level.

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 parameter descriptions. The description adds value by linking 'agree_to_terms' to the client agreement requirement and explaining the expiration context for the UUID, going beyond schema basics.

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 states it books a trade using a broker quotation UUID, which is a specific verb+resource pair. It also distinguishes from sibling tool 'refresh_quote' by mentioning expiration and alternative action.

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?

Provides explicit when-to-use context (book a trade) and an alternative tool ('refresh_quote') for expired quotations, meeting the criteria for high usage guidance.

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