ebay_get_ad_report_metadata

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

No annotations are provided, so the description carries full burden. It states it returns metadata but does not explicitly disclose it is a read-only operation with no side effects. Basic behavioral understanding is achievable but could be more explicit.

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?

Two sentences, no excess words. Front-loaded with the core action and short return description. Every sentence adds value.

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 no parameters, the description is sufficiently complete. It describes the purpose and return contents. Could potentially mention that metadata is for ad reports, but sibling context indicates this.

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?

No parameters exist, so the description does not need to add param info. Schema coverage is 100% (empty schema). The description adds no redundant parameter details, meeting the baseline for zero parameters.

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?

Clearly states the tool retrieves metadata for all report types and lists return types (dimensions, metrics, filters). Distinguishes from sibling 'ebay_get_ad_report_metadata_for_type' which targets a specific type.

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?

Implied usage: for obtaining an overview of all report metadata. No explicit when-to-use or alternatives guidance, but the sibling tool name provides contrast. Lacks explicit context like 'use this before creating a report'.

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