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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It notes the prerequisite for order_secret but does not describe the consequences of cancellation (e.g., destructive, irreversible) or any side effects. For a cancel operation, this is insufficient.

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 concise—two short sentences with no fluff. It front-loads the primary action and adds a necessary prerequisite. However, the brevity may contribute to under-specification, but that is a matter of other dimensions. For structure, it is efficient and well-ordered.

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?

For a cancellation tool with no annotations and no output schema, the description is incomplete. It does not explain when cancellation is appropriate, what happens to the order after cancellation, any authentication or authorization requirements beyond the secret, or error scenarios. An agent would struggle to use it correctly.

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?

The schema has no descriptions for order_id or order_secret, and the description only adds meaning for order_secret by noting it comes from create_limit_order. order_id remains undefined. Since schema coverage is 0%, the description does not fully compensate, leaving both parameters under-documented.

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 action: 'Cancel a limit order.' This is a specific verb and resource. However, it does not differentiate this tool from siblings such as fill_limit_order or limit_order_status, which could also relate to limit orders. The clarity is good but not complete.

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 provides no guidance on when to use this tool versus alternatives. It only mentions that order_secret is required from create_limit_order, but does not outline conditions for cancellation or when not to use it. This is a significant gap.

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