ebay_get_item_promotion

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Get details' which implies a read operation, but does not explicitly confirm it is read-only, mention authentication requirements, rate limits, or any side effects. The description is insufficiently transparent.

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 with no extraneous content. It is concise and front-loads the purpose. However, it could be slightly expanded to include critical context without becoming verbose.

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, no annotations) and the presence of many sibling tools, the description is insufficiently complete. It lacks differentiation from related tools like ebay_get_promotions and does not explain what constitutes an 'item promotion' or what the response contains.

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?

The input schema has 100% description coverage for the single parameter (promotionId described as 'Promotion ID'). The description adds no extra meaning beyond the schema. At baseline 3, it is adequate but does not enhance understanding of how to obtain or format the promotion ID.

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 'Get details of a specific item promotion' clearly identifies the action (get) and resource (details of item promotion). It is specific enough to convey the tool's function, but lacks differentiation from sibling tools like ebay_get_promotions or ebay_get_item_price_markdown_promotion, which also retrieve promotion-related data.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., ebay_get_promotions for listing all promotions), nor does it mention any prerequisites or scenarios where this tool is appropriate.

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