ebay_get_report_metadata

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

No annotations provided, and the description gives no behavioral context: no mention of read-only nature, required permissions, rate limits, or what triggers errors. This is a significant gap for a tool without annotations.

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?

Extremely short (one sentence) but under-specified. It is not concise in a useful way; it omits critical information that would fit in a few more sentences.

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?

With no output schema and no annotations, the description fails to explain what report metadata is returned, the data format, or any constraints. Given the complex eBay tool ecosystem, this is insufficient for effective tool selection.

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% (2 parameters), so baseline is 3. The description adds no extra meaning beyond the schema, but the schema descriptions themselves are poor ('channel optional endpoint parameter'). The description does not compensate.

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 states verb+resource ('Get report metadata'), but is vague. It doesn't distinguish from sibling tools like ebay_get_report_metadata_for_report_type, so the agent cannot easily understand the exact scope.

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 vs alternatives. There is no explanation of prerequisites, when to choose this over ebay_get_report or ebay_get_report_metadata_for_report_type.

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