delete_shipping_zone_method

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

The annotations already include 'destructiveHint: true,' so the description adds no further behavioral context. It does not mention irreversibility, the 'force' requirement, or any side effects, offering no value beyond what structured annotations already provide.

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 a single, front-loaded sentence with no filler words. Every part is essential and directly conveys the operation.

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 tool is a straightforward delete with full schema coverage and a destructive annotation. The description, while minimal, is sufficient given the structured data. It could mention the 'force' requirement, but the schema already handles that, so the overall context 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?

Input schema descriptions cover 100% of parameters (zone_id, instance_id, force, fields). The description adds no parameter-specific meaning, so the baseline score of 3 applies because the schema already documents each parameter clearly.

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 'Remove' with a clear resource 'a shipping method from a zone,' which precisely matches the tool name. It distinguishes this operation from siblings like 'delete_shipping_zone' and 'add_shipping_zone_method.'

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, such as using 'update_shipping_zone_method' or when a shipping method cannot be deleted. There are no exclusions, prerequisites, or contextual hints beyond the basic action.

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