cancel_stock_order_by_id

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

No annotations exist, so the description carries full burden. It provides no behavioral details such as whether cancellation is immediate, if there are side effects, or error conditions. Only states the action without any transparency.

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 very short (one sentence plus a parameter description). It is efficient but too terse, missing critical information. Not ideal conciseness as it sacrifices completeness.

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 an order cancellation tool and the existence of an output schema (unseen), the description should explain expected success/error responses, but does not. Sibling tools indicate a rich ecosystem, but this description lacks context.

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%, but the description explains order_id is 'The ID of the order to cancel', adding minimal meaning beyond the schema's title and type. No format, source, or constraints are given.

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 it cancels a specific stock order. The verb 'cancels' and resource 'stock order' are specific. However, it does not explicitly differentiate from sibling tools like cancel_all_stock_orders or cancel_option_order_by_id, though the 'by_id' in the name implies single order cancellation.

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?

No guidance on when to use this tool versus alternatives. No prerequisites, context, or conditions are provided. The description lacks any 'when to use' or 'when not to use' information.

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