ghl_payment_coupon_create

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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with creation. The description adds OAuth scopes and endpoint details, but does not disclose failure modes, idempotency limitations, or side effects beyond creation. Adequate but not thorough.

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 endpoint and OAuth scopes. It is front-loaded with the title and a clear explanation. However, it is slightly redundant (title repeated) and could be tightened by removing minor fluff. Still efficient overall.

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 has a complex input schema with nested objects, but the description does not explain the return value or error conditions. For a creation tool, it would be helpful to mention what is returned (e.g., created coupon ID). Lacks completeness for full agent guidance.

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 description coverage is 100%, so the schema already documents all parameters. The description mentions 'discount amount, validity period, usage limits, and applicable products' but adds no new meaning beyond what is in the schema. Baseline score of 3 is appropriate.

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 creates a new promotional coupon, which is a specific verb+resource combination. It inherently distinguishes from sibling tools like ghl_payment_coupon_delete/get/list/update by focusing on creation. No vague language.

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 advises using the endpoint to set up promotional offers and discounts, which provides general context. However, it does not specify when to avoid using this tool or mention alternatives (e.g., when to use update instead). No explicit exclusion criteria.

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