ebay_delete_item_promotion

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

With no annotations, the description must fully disclose behavior, but it only states the action. It omits critical details: whether deletion is irreversible, if it requires the promotion to be inactive, or how it affects active listings. This is a significant gap for a write operation.

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, which is concise, but it merely repeats the tool name ('Delete an item promotion'). While not verbose, it lacks informative content, making it minimally acceptable.

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 simplicity (one parameter, no output schema), the description should at least mention irreversible effects or prerequisites. Without this, the agent lacks essential context to use the tool correctly.

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% for the single parameter 'promotionId', but the description adds no additional meaning beyond the schema's minimal 'Promotion ID'. Baseline of 3 is appropriate as the schema already documents the parameter.

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 'Delete an item promotion' clearly states the action (delete) and resource (item promotion). It distinguishes from sibling tools like 'ebay_delete_item_price_markdown_promotion' by referring specifically to 'item promotion', though it could be more precise about the promotion 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?

No guidance is provided on when to use this tool versus alternatives like pausing a promotion (ebay_pause_item_promotion) or deleting a markdown promotion. There are no examples or context regarding prerequisites or expected states.

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