ghl_store_delete_shipping_zone

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

The annotations already declare destructiveHint: true, indicating data modification. The description adds the endpoint and ID but no additional behavioral context (e.g., irreversibility, cascading effects). No contradiction with 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 short and includes the endpoint, which is useful. However, the second sentence is redundant with the first. Could be more efficient by merging.

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 simple delete with 3 parameters and annotations, the description covers the ID but misses explanation of altId and altType. The endpoint detail helps but does not fully compensate for missing parameter semantics.

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 description mentions only shippingZoneId, ignoring altId and altType. The schema description for shippingZoneId is misleading ('ID of the item that needs to be returned' suggests retrieval, not deletion). The description adds no value beyond the schema.

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 shipping zone' and specifies the action with the ID parameter, making the purpose unmistakable. It is distinct from sibling tools like ghl_store_delete_shipping_carrier or ghl_store_update_shipping_zone.

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?

There is no guidance on when to use this tool vs. alternatives. It does not mention prerequisites, when not to use it, or provided a comparison with other shipping zone operations.

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