promotions_codes_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it lists codes and includes a spec link, but does not elaborate on any behavioral traits beyond what annotations provide. No extra context on pagination, limits, or authorization is given.

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, concise sentence that front-loads the core purpose. Every word is informative; no redundancy. The spec link is appended without cluttering the main purpose.

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 simple listing tool with one parameter and no output schema, the description is adequate but not comprehensive. It lacks details on response format, pagination, error handling, and prerequisites. Given the annotations cover safety, the description is minimally sufficient.

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 0% (no description for promotionId in schema). The description hints that promotionId must be for a single-use promotion, but does not fully explain the parameter's format, constraints, or how to obtain it. The description only partially compensates for the lack of schema documentation.

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 it lists single-use codes for a SINGLE_USE_PROMOTION, using the verb 'list' and specifying the resource 'single-use codes'. It distinguishes from siblings like promotions_list (lists promotions) and promotions_codes_create (creates codes) by specific resource type.

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 implies that the tool is for single-use codes of a SINGLE_USE_PROMOTION, but does not explicitly state when to use it versus alternatives like promotions_list or promotions_code_get. No explicit when-not-to-use or prerequisites are mentioned.

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