store_delete_shipping_zone

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

The description adds no behavioral information beyond what the annotations already provide. Annotations indicate destructiveHint=true and idempotentHint=true, but the description does not elaborate on the consequences of deletion, such as whether associated rates are removed or if the action is irreversible. It simply states the action.

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 one short, clear sentence without any fluff. It is appropriately sized for a straightforward delete operation and front-loads the essential action.

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 is minimal and does not provide context about the operation's effects, such as whether it deletes associated shipping rates or how it interacts with the location context. While the schema covers the parameters, the description does not explain the operational impact or success criteria. For a destructive action, this is a notable gap.

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 description covers all parameters (100%), so the baseline is 3. The description does not add any extra clarity about parameters; it merely names the tool. The parameter descriptions in the schema already explain altId and altType, though the shippingZoneId description is oddly worded as 'ID of the item that needs to be returned' which is a bit off for deletion.

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 (delete) and the resource (shipping zone), which is specific and distinguishes it from sibling tools like store_delete_shipping_carrier or store_delete_shipping_rate. It is unambiguous and to the point.

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 does not mention any prerequisites, conditions, or scenarios where this tool is appropriate. The agent must infer that it is for deleting shipping zones from the name alone.

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