ebay_get_vero_report_items

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

No annotations are provided, so the description must carry the full behavioral disclosure. It correctly identifies this as a read operation (get), but it does not mention any security requirements (e.g., authentication scopes), rate limits, or whether the report must exist. However, the description is accurate and non-misleading.

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, well-structured sentence that front-loads the main purpose, then lists key features. It is efficient but could be slightly more structured (e.g., separating pagination details).

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?

The description is adequate for a simple read tool, but it does not explain what the returned items contain (no output schema). It also lacks details like prerequisites (e.g., an existing VERO report) or whether the tool returns a list or a single item. Given no output schema, more completeness would be helpful.

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 3 parameters (limit, filter, offset) with 0% description coverage. The description says 'supports filtering, pagination via limit and offset parameters' but does not explain the format or expected values of filter (e.g., a query string syntax). limit and offset are vaguely described. This adds minimal value over the schema.

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 clearly states the tool retrieves VERO report items (listings reported for intellectual property infringement), which is a specific and unique resource. It distinguishes from sibling tools like ebay_create_vero_report or ebay_get_vero_reason_code by focusing on items within a 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?

The description mentions filtering and pagination support, implying these are the primary use cases, but it does not explicitly state when to use this tool versus alternatives (e.g., ebay_get_vero_report for the report itself). No when-not or alternative guidance is provided.

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