delete_shipping_zone

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

Annotations include destructiveHint: true, so the agent knows it's destructive. The description adds valuable context by disclosing what gets destroyed ('all methods and locations in the zone'), going beyond the annotation. It does not mention the force parameter requirement, but the schema covers that.

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?

Two sentences, efficiently front-loaded with the primary action and a critical detail about cascading deletion. No unnecessary words or repetition.

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?

The description covers the main effect and cascade behavior, which is adequate for a simple delete tool with annotations. It does not explain return values (no output schema) or the force parameter, but those are defined in the schema. For its complexity, it is complete enough.

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 100%, with descriptions for id, force, and fields. The tool description does not add any additional parameter semantics beyond the schema; it only explains the effect of deletion, not the parameters themselves. Baseline 3 is appropriate.

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 'Delete a shipping zone' with a specific verb and resource, distinguishing it from sibling tools like update_shipping_zone, get_shipping_zone, and delete_shipping_zone_method. The cascade effect ('removes all methods and locations') adds further specificity.

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 when to use the tool (to delete a shipping zone) but does not explicitly say when not to use it or provide alternatives. There is no mention of using update_shipping_zone to disable instead, or any other usage context beyond the inherent purpose.

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