ebay_get_ad_report

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

No annotations provided. Description lacks behavioral details such as read-only nature, authentication requirements, error conditions for incomplete reports, or download format. The phrase 'Download' implies read operation but not explicitly stated.

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?

Description is extremely concise at 10 words, front-loading the verb and resource. Could include more context without being verbose, but no unnecessary information.

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?

Description is insufficient for a 1-param tool with no output schema and no annotations. It fails to explain the report lifecycle (create, wait, download), output format, or related tools for report creation.

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 one parameter 'reportId' described as 'Report ID'. Description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 uses specific verb 'Download' and resource 'completed ad report' with clear identifier 'by report ID'. It clearly distinguishes from sibling tools like ebay_get_ad_report_metadata and ebay_get_report.

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 like ebay_get_report_task or ebay_get_ad_report_metadata. No mention of prerequisites (e.g., report must be completed via ebay_create_report_task) or when not to use.

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