ebay_get_promotion_reports

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

The annotations already indicate readOnlyHint=true, so the safe-read nature is known. The description adds no behavioral context beyond the trivial statement that it 'gets' reports—no mention of pagination, return format, filtering semantics, or rate limits. It provides no additional transparency over the annotation.

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 without fluff, but the phrase 'through the eBay Marketing API' is redundant and doesn't earn its place. It is concise yet not informationally efficient, as it repeats the tool's name and adds no useful context.

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 no output schema and a simple two-sentence description, this tool is under-specified for practical use. It lacks details about the kind of report data returned, available promotion types, parameter purpose, and any prerequisites or limits. The 100% schema coverage helps with parameter names, but not with usage context.

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%, so the schema documents all 6 parameters. The description adds no parameter meaning beyond what the schema already provides, which is a baseline 3. There is no extra clarification of what the parameters represent or how they interact.

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 states a clear action ('Get') and resource ('promotion reports'), so an agent understands what the tool does. However, it does not differentiate from sibling tools like ebay_get_promotion_summary_report or ebay_get_report, which also deal with reports, leaving ambiguity in selection.

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 about when to use this tool versus alternatives. It only mentions the eBay Marketing API, which is trivial given the tool's prefix and sibling context. No exclusions, prerequisites, or decision criteria are provided.

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