ghl_store_delete_shipping_carrier

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

Annotations provide destructiveHint: true and idempotentHint: true. The description adds only endpoint detail, not behavioral context such as side effects (e.g., cascading deletions) or required permissions. With annotations present, the description's additional value is minimal.

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?

Description is concise with three lines, each adding value: action, parameter, and endpoint. The endpoint detail is somewhat redundant but not excessive. Efficiently communicates the core purpose.

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?

Lacks context about prerequisites (e.g., carrier must exist) and consequences (e.g., impact on shipping rates). The required altId and altType parameters are not explained in the description, leaving ambiguity about their purpose. A complete description would address these gaps.

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 67% (2 of 3 parameters have descriptions). The description mentions shippingCarrierId but does not add meaning for altId or altType beyond what the schema provides. It fails to compensate for the missing parameter description.

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?

Description clearly states the action 'Delete shipping carrier' and identifies the key parameter (shippingCarrierId). However, it does not distinguish from sibling tools like ghl_store_get_shipping_carrier or ghl_store_update_shipping_carrier, which have similar descriptions but different actions.

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?

No guidance on when to use this tool versus alternatives. The description only states what it does, without mentioning when deletion is appropriate or any prerequisites.

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