delete_standing_order

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

Beyond the annotations (destructiveHint=true), the description adds crucial behavioral details: pausing preserves the order and history, deleting removes both, neither operation costs tokens, and a paused order still counts against the plan limit. This explains side effects and resource constraints not present in the annotations.

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 three sentences that front-load the primary action, then efficiently explains the alternative and its consequences. Every sentence adds distinct value without redundancy.

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 presence of an output schema, the description needn't explain return values. It covers delete and pause/resume semantics, state effects, cost, and plan limit implications, making it complete for the tool's complexity.

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 input schema already describes the active parameter's behavior (omit to delete, false to pause, true to resume) with 100% coverage. The description adds extra nuance about plan limit usage and the fact that pausing keeps history, which is not in the schema. This supplements the schema 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?

The description begins with a specific verb ('Delete') and resource ('standing order'), clearly stating the primary action and also mentioning the alternative pause/resume behavior. It distinguishes from sibling tools like create_standing_order and list_standing_orders by focusing on the delete/pause operation.

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 explicitly states when to delete vs pause: 'delete rather than pause when you want the slot back.' It also provides the context that pausing keeps the order/history and that neither operation costs tokens, giving clear decision guidance.

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