create_promotion

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

The description adds that the tool creates a new promotion and returns the created resource, which is consistent with annotations (readOnlyHint=false, destructiveHint=false). However, it does not disclose additional behavioral traits such as side effects or prerequisites beyond what annotations already convey.

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 short and front-loaded, with minimal redundancy. The header line repeats some information but does not significantly hinder conciseness.

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 nested input schema and lack of output schema, the description provides adequate context but could be more complete by explaining constraints or required fields. The resource response is noted, which helps.

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?

All parameters are described in the input schema (100% coverage), so the description does not add value beyond the schema. Baseline score of 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 clearly states the tool creates a promotion without coupons, using a specific verb and resource. It distinguishes itself from sibling tools like create_coupon_promotion by explicitly noting the absence of coupons.

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 usage for creating promotions without coupons but does not explicitly mention when to use alternatives or when not to use this tool. The sibling list includes related tools, but no guidance is provided.

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