ebay_get_traffic_report

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It fails to mention whether this is a read-only operation, what the output format is, whether it requires authentication, or any rate limits. For a tool that retrieves data, these are critical gaps.

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, short sentence, which is concise but lacks substance. It is not structured to convey key information efficiently. While it avoids verbosity, the minimalism reduces utility.

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 the absence of an output schema and annotations, the description should provide more context about the report's structure, available metrics and dimensions, and how they interact. The current description is insufficient for an agent to understand the tool's full capabilities and limitations.

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?

The input schema has 100% description coverage, with each parameter already documented (e.g., 'metric: Metrics to retrieve...'). The tool description adds no additional meaning beyond the schema. According to guidelines, baseline 3 is appropriate when schema coverage is high.

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 'Get traffic report for listings', which gives a verb and a general resource. However, it lacks specificity about what constitutes a 'traffic report' (e.g., impressions, clicks) and how it differs from other similar report tools like ebay_get_report or ebay_get_ad_report. The purpose is vague and does not clearly distinguish from siblings.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or cases where other report tools should be preferred. Given the large number of sibling tools with similar names (ebay_get_report, ebay_get_promotion_report), this omission makes selection difficult.

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