cumulus_coupons

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

With no annotations, the description carries the full burden and does disclose two behavioral facts: authentication is required and the result is limited to activated/available coupons. It does not state that the call is read-only and non-mutating, nor anything about result volume or ordering.

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 short sentences, front-loaded with the resource and followed by the auth prerequisite. No wasted wording, though the terse phrasing leaves no room for the parameter clarification that is needed.

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?

An output schema exists, so return values need not be explained, and the login prerequisite covers the main usage constraint. The unresolved gap is the two undocumented boolean flags, which for a simple read tool is the one thing an agent most needs help with.

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 0%: 'full' and 'with_preview' are bare booleans with defaults and the description says nothing about either. An agent has to guess that 'full' widens the payload and 'with_preview' controls preview data, which is exactly what the description should have settled.

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?

Names the specific resource (Cumulus coupons) and narrows scope with the parenthetical '(activated and available)', so an agent knows what set it returns. It does not distinguish itself from the singular sibling cumulus_coupon or from partner_coupons, leaving some ambiguity for selection.

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?

'Requires login' gives a concrete prerequisite for calling it, which is genuinely useful. However, there is no guidance on when to use this list versus cumulus_coupon (presumably a detail view) or partner_coupons, and no note on when-not-to-use it.

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