sell_stock_market

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

With no annotations, the description carries full burden but only states the purpose. It does not disclose execution details, potential failures (e.g., insufficient shares), or order lifecycle. No mention of what the output contains.

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?

The description is short and uses an 'Args:' format for clarity. However, it could be more structured with separate lines for each parameter and additional context.

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 complexity of order execution and many sibling tools, the description is incomplete. It omits prerequisites (owning the stock), execution timing, order ID returns, and potential risks. The output schema exists but is not leveraged in the description.

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 0%, so description must compensate. It adds basic explanations (symbol is stock symbol, quantity is number of shares) but does not clarify constraints like positive integer for quantity or valid ticker symbol.

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 'Places a market sell order for a stock,' specifying the verb and resource. It distinguishes from sibling tools like buy_stock_market (buy vs sell) and sell_stock_limit (market vs limit).

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?

The description implies use for immediate execution at market price but provides no explicit guidance on when to use this tool versus alternatives like sell_stock_limit or sell_stock_stop_loss. No prerequisites or exclusions are mentioned.

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