promotions_list_paged

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

Beyond annotations (readOnly, idempotent, etc.), the description reveals response structure, pagination mechanism differences, and a critical warning about response size exceeding caps and spilling to temp files. This goes beyond what annotations alone provide.

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 a single, well-organized paragraph that starts with the core purpose, then adds critical guidance, platform specifics, and a caveat. Every sentence adds value; no fluff.

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 complexity (9 parameters, pagination differences, response size issues), the description covers all essential aspects: purpose, alternative, return format, platform behavior, and a precaution. No output schema, but the return structure is described sufficiently.

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 56%, but the description adds meaningful context about pagination parameters (offset/limit vs nextId/prevId) and advises a modest limit. It does not detail each parameter individually, but the overall guidance compensates well for the gaps.

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 lists promotions with pagination and strongly distinguishes it from the non-paged sibling 'promotions_list' by warning about timeouts. The verb 'list' and resource 'promotions' are specific.

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?

Explicitly recommends this tool over 'promotions_list' due to timeout risk. Also explains platform-specific pagination behavior (Cloud vs Server/DC), guiding proper parameter usage.

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