partner_coupons

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It does disclose the authentication requirement, which is genuinely useful, but says nothing about whether this is a read-only listing, what it returns, or any rate/side-effect behavior.

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?

Two very short sentences, front-loaded and free of padding, so nothing needs trimming. However, the brevity reflects under-specification rather than efficient communication.

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 presence of an output schema means return values need not be described, but the definition still fails to distinguish this tool from its near-identical siblings or explain its sole parameter. For a tool in a dense coupon cluster, that leaves an agent without enough to select it correctly.

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 single optional boolean parameter 'full' has 0% schema description coverage and is never mentioned in the description, so an agent cannot know what toggling it does. With low coverage the description was expected to compensate and does not.

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 'Cumulus partner coupons' essentially restates the tool name, adding only the domain label 'Cumulus'. There is no verb indicating what operation is performed (list? fetch? activate?) and no differentiation from the closely named siblings cumulus_coupons and cumulus_coupon.

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 choose this over cumulus_coupons or cumulus_coupon is given. The only contextual hint is 'Requires login', which is a prerequisite rather than a usage rule, and even that omits what to do when unauthenticated.

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