ebay_get_item_promotion

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

The annotations already convey readOnlyHint=true, and the description adds no behavioral context beyond naming the Marketing API. It does not describe response shape, authorization needs, errors, or scope, so it fails to add value beyond the structured data.

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 brief and front-loaded, which is good for conciseness. The phrase 'through the eBay Marketing API' adds little selection value and contributes to the overall sparse context, keeping this from a perfect score.

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?

Despite the low parameter complexity, the tool sits among many promotion endpoints and has no output schema. The description leaves the agent unable to understand what an item promotion is, how the returned data looks, or how promotionId should be obtained and used.

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 100%, but the parameter description is tautological ('promotionId required endpoint parameter'). The baseline of 3 applies because the schema already names and types the parameter, but the description contributes no additional semantic 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?

The description uses a clear verb and resource ('Get item promotion') and states the relevant API. However, it does not distinguish this from sibling promotion tools such as ebay_get_item_price_markdown_promotion or ebay_get_promotions, so it falls short of full sibling differentiation.

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?

There is no guidance on when to use this tool versus the many promotion-related alternatives, no prerequisites, and no exclusions. The only hint is the word 'item promotion', which the agent must interpret without additional context.

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