promotions_create

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

Annotations indicate destructiveHint: true, and the description reinforces this by stating 'promo code becomes redeemable by customers.' This adds context beyond annotations. However, it does not discuss idempotency or other behavioral traits explicitly, but annotations cover those.

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 extremely concise: two sentences and a link. It front-loads the core action and required fields. Every word earns its place, with 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?

For a complex tool with 13 parameters and dependencies, the description is too brief. It lacks explanation of parameter relationships, output behavior, and edge cases. Although the schema and annotations provide some context, the description does not sufficiently compensate for the tool's complexity.

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 54%, yet the description only lists required fields without adding new meaning. It does not explain parameter interactions or provide context for undocumented parameters. The schema itself has descriptions for most parameters, so the description adds minimal value.

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?

Description clearly states 'Create a new promotion' with a specific verb and resource. The 'PUBLIC IMPACT' line adds clarity about the effect. It distinguishes from sibling tools like promotions_update and promotions_codes_create by focusing on creation.

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 lists required fields but offers no explicit guidance on when to use this tool versus alternatives like promotions_update or promotions_codes_create. It does not provide when-not or exclusion criteria, which would be helpful given the many sibling tools.

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