getCustomerCoupons

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It does not mention that the operation is read-only (though likely), whether authentication is required, what the response format looks like, or if there are any side effects. The description is completely silent on these critical aspects.

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?

While the description is extremely short, it is under-specified rather than concise. It does not provide the necessary information about the tool's function or usage, so the brevity is a defect, not a virtue.

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?

Given the tool has no output schema, no annotations, and minimal description, the context is wildly incomplete. An agent cannot infer what this tool returns, any pagination or filtering behavior, or how it relates to other coupon or customer tools. The description is inadequate for even basic use.

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 includes a single parameter, customerId, but the description provides no explanation of its meaning, format, or how it affects results. With schema description coverage at 0%, the description must compensate, but it fails to add any value beyond the bare schema type.

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 'Get coupon' uses a verb and a resource, but is extremely vague—it does not specify that it retrieves coupons for a customer, what type of coupons, or how the customerId relates. It does not distinguish itself from sibling tools like getCustomerBalance or getCustomerDetails, and reads more like a label than a functional description.

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 zero guidance on when to use this tool, what problem it solves, or when to prefer an alternative. No context is given for typical use cases or exclusions, making it impossible for an agent to decide when this tool is appropriate.

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