quote_stock_trade

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

Annotations declare readOnlyHint=true; description adds that it is time-limited and uses Uniswap, and explicitly states it never signs or submits. No contradiction. Adds useful context beyond annotations.

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-loaded with purpose and key behavioral trait. No redundant information. Every word earns its place.

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, the description does not explain the return structure (e.g., quote details, expiry). It mentions 'time-limited' but remains vague. For a 5-parameter tool with varying schema coverage, missing return info and parameter overview reduces completeness.

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 description coverage is 60%, with some parameters having no description (tokenId). The tool description does not elaborate on parameters, leaving the schema to do the work. Could be improved by explaining tokenId or slippage.

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 verb 'request a quote', the resource 'Uniswap quote for stock tokens held by a StonkBroker TBA', and specifies it is for exact-input trades. This distinguishes it from the sibling 'execute_stock_trade' which signs/submits.

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 notes this should be used for getting a quote before execution, and that it never signs or submits. Implies when-not-to-use (for actual execution) and contrasts with execute_stock_trade. Could be more explicit about prerequisites.

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