ghl_payment_coupon_delete

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

Annotations indicate destructive=true and idempotent=true. The description reinforces permanence ('Permanently deletes', 'cannot be undone') and explains downstream effects (checkout links stop working). No contradictions 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 somewhat verbose, repeating the tool name and including technical endpoint details (URL, version header, OAuth scopes) that could be shortened. The key information is front-loaded but could be more concise.

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 delete tool without output schema, the description adequately covers the action's irreversibility and impact on checkout links. It also includes OAuth scope requirements. However, it could mention potential error cases or prerequisites.

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 input schema has 100% description coverage for the nested parameters (id, altId, altType), so the description does not need to add much. It does not provide extra context beyond what the schema already describes.

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 tool is for permanently deleting a coupon and explains the effect on checkout links. It distinguishes from sibling tools like create, get, list, and update by focusing on deletion.

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 clear usage scenarios: discontinuing promotional offers or cleaning up unused coupons. It also warns that the action cannot be undone. However, it does not explicitly state when not to use or suggest alternatives.

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