ebay_get_item_price_markdown_promotion

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

No annotations are provided, so the description must cover behavioral traits. It only says 'Get details', implying a read operation, but does not disclose any potential side effects, authorization needs, rate limits, or response characteristics. The description is insufficient for full transparency.

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 concise sentence (8 words) that front-loads the purpose. No wasted words, but could slightly expand to add usage context without becoming verbose. Good for a simple tool.

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?

For a simple get-by-ID tool with one parameter and no output schema, the description minimally covers the action. However, it could be improved by providing hints about the return value or common use cases. Given the lack of annotations and schema details, it is adequate but not complete.

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% (promotionId with description 'Promotion ID'), so baseline is 3. The description adds no additional meaning beyond the schema; it does not explain how to obtain the promotionId or any format constraints. No extra value beyond the schema.

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 action ('Get details') and the specific resource ('item price markdown promotion'), with 'specific' indicating a single item. This distinguishes it from sibling tools like 'ebay_get_promotions' (list) or 'ebay_delete_item_price_markdown_promotion' (delete).

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 on when to use this tool versus alternatives such as 'ebay_get_item_promotion' or 'ebay_get_promotions'. No prerequisites, exclusions, or context for the promotionId are mentioned. The description lacks any usage direction beyond stating the basic function.

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