ebay_get_promotions

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 mentions optional filters and return types, but does not disclose pagination behavior, read-only nature, rate limits, or any side effects. Critical gaps for a get-all tool.

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 extremely concise (one sentence), but it front-loads the core purpose. Additional structure (e.g., bullet points for filters or return details) would improve scannability, but current length is efficient.

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?

No output schema exists, so description should hint at return structure. It provides examples ('order discounts, shipping discounts') but does not address pagination (despite limit/offset parameters) or the overall response shape. Adequate but incomplete for a complex tool.

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% with clear descriptions for all five parameters. The description adds no extra meaning beyond 'optional filters', so baseline 3 applies. It does not compensate for missing schema coverage since coverage is complete.

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?

Description clearly states the verb ('Get'), the resource ('all item promotions'), and the scope ('optional filters'). Examples of return types ('order discounts, shipping discounts') help clarify what kind of promotions are retrieved, distinguishing it from singular promotion retrieval tools like ebay_get_item_promotion.

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., ebay_get_item_promotion, ebay_get_promotion_report). It implies usage for listing promotions with filters, but lacks exclusions or comparative context.

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