ebay_create_item_promotion

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create a new item promotion,' implying a write operation, but does not mention required permissions, rate limits, effects on existing promotions, or any side effects. This is insufficient for safe and correct tool invocation.

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 concise with a single sentence, but it is overly minimal. While it avoids fluff, it sacrifices critical information. It earns its place but could benefit from additional sentences for context without losing 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 tool's single parameter (a complex nested object) and the presence of many sibling promotion tools, the description is incomplete. It does not explain the meaning of 'item promotion,' the structure of the 'promotion' object, or how this tool fits among related tools like 'ebay_create_item_price_markdown_promotion' or 'ebay_get_item_promotion'.

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% as the 'promotion' parameter has a description ('Promotion configuration with discountRules, inventoryCriterion, etc.'). The tool description adds no additional parameter information. Since the schema already provides meaning, a baseline of 3 is appropriate, though the description could have elaborated on parameter structure or constraints.

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 states 'Create a new item promotion' and gives examples like order discount and volume pricing, which clarifies the verb and resource. However, it fails to distinguish this tool from its sibling 'ebay_create_item_price_markdown_promotion', which also creates promotions but with a specific type. This lack of differentiation reduces clarity.

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 such as 'ebay_create_item_price_markdown_promotion' or other promotion management tools. It lacks any 'when to use' or 'when not to use' information, making it difficult for an agent to select the correct tool.

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