get_promotions_coupons

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

Annotations already declare readOnlyHint and idempotentHint, but the description goes well beyond them: it discloses server-side auth injection, throttling under LearnWorlds' 30-per-10s cap, retry behavior on 429/5xx, and the exact error semantics for 401/403/404/422. Nothing contradicts the 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 organized into labeled sections (Behavior, Returns, Use when, Related) and front-loaded with the read-only indicator and endpoint. Each sentence adds distinct information with no filler or repetition of the schema.

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 single-parameter read-only tool with no output schema, the description covers everything needed to invoke it correctly: scope, return format, error handling, safety profile, throttling behavior, and usage guidance. There are no meaningful gaps.

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 coverage is 100% with 'Promotion Id' documented, so the schema carries the parameter meaning. The description adds only that the pid selects which promotion's coupons are returned, which is marginal added value; baseline 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 states a specific verb and resource: 'Returns all coupons for the promotion specified by the provided promotion id.' It clearly identifies the endpoint and the parameter that selects the result set, leaving no ambiguity about what the tool does.

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?

Explicit 'Use when' guidance says it is safe for speculative lookups and reporting, and states what it is not for: 'Not for changing anything — use the matching 🟡 write tool.' It also names the related Promotions tools, helping an agent route to alternatives.

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