ebay_create_item_promotion

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Create a new item promotion' without detailing side effects, required permissions, whether the promotion is immediately active, or if it can be modified. This is insufficient for a mutation tool.

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 sentence, highly concise and front-loaded. It could be slightly improved with additional context without becoming verbose, but it is efficient for the basic 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?

Given the complexity (nested object parameter, many sibling tools, no output schema), the description fails to provide sufficient context. It does not mention return values, prerequisites (e.g., existing inventory items), or how this promotion relates to other promotion management tools. This leaves the agent underinformed.

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 the 'promotion' parameter described as 'Promotion configuration with discountRules, inventoryCriterion, etc.' The description adds context by listing order discount and volume pricing as example promotion types, but does not elaborate on the parameter structure beyond what the schema already provides. Baseline 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 new item promotion and gives examples like order discount and volume pricing, which clarifies the resource type. However, it does not differentiate from sibling tools such as ebay_create_item_price_markdown_promotion, which suggests a potential overlap.

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 provides no guidance on when to use this tool versus alternatives like ebay_create_item_price_markdown_promotion or bulk creation tools. It lacks explicit when-to-use, when-not-to-use, or prerequisite information.

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