nt_cancel_order

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

With no annotations, the description carries full burden for behavioral disclosure. It states the action (cancel) but does not disclose side effects, irreversibility, error behavior, or prerequisites. An agent cannot infer what happens if the order is already filled, whether cancellation is permanent, or what the response 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?

One sentence, directly to the point, no redundant words. The description is front-loaded with the verb and clearly scoped.

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 one-param tool with no output schema and no annotations, the description is minimally adequate but lacks context about outcomes, conditions, and error handling. It doesn't explain what 'working order' means or what happens on cancellation, but for a simple tool it is not severely under-specified.

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 a single string param 'orderId' with no description, so coverage is 0%. The description's 'by its ID' clarifies that orderId is the identifier of the working order, providing minimal additional meaning. This is sufficient for the simple param but doesn't offer format or domain-specific details.

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 uses a specific verb 'Cancel' with a specific resource 'specific working order' and a qualifier 'by its ID', clearly distinguishing it from siblings like nt_cancel_all_orders and nt_modify_order.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. For example, it does not direct users to nt_cancel_all_orders for bulk cancellation. The only clue is the word 'specific' which implicitly contrasts with the sibling tool, but no explicit when-to-use guidance is provided.

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