execute_stock_trade

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

Beyond annotations (destructiveHint=true), description reveals it auto-posts balance deltas and transaction link to X. However, does not disclose handling of failures or X posting errors.

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?

Single sentence front-loads the action and key steps. Efficient, but could benefit from structured list for clarity. 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?

Covers side effect (X post) and destructive nature, but lacks return value description, failure scenarios, or integration with sibling tools for status checks. Adequate but not thorough.

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 0%. Description does not explain 'quoteId' or 'confirmation' parameters. 'confirmation' with const 'EXECUTE' is not mentioned, leaving agents to infer meaning.

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?

Clearly states the tool executes a previously quoted trade from the StonkBroker ERC-6551 wallet, waits for confirmation, and posts results to X. Differentiates from sibling 'quote_stock_trade' which provides the quote.

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?

Implies a prior quote is needed but does not explicitly state when not to use this tool or mention alternatives for retrying or checking status. No exclusionary guidance.

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