ebay_get_vero_report

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

With no annotations, the description should disclose behavioral traits. It does not mention idempotency, side effects, error handling, permissions, or what happens if the report does not exist.

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 sentence with no unnecessary words. However, it is slightly under-specified for a tool with no output schema or annotations.

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 one parameter, the description should at least mention what the tool returns or prerequisites. It misses both, leaving the agent without needed context.

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 single parameter 'veroReportId' is fully described in the schema as 'VeRO report identifier returned by createVeroReport'. The description adds no new meaning beyond 'by ID', so the baseline of 3 applies (schema covers 100%).

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 'Get a specific VERO report by ID' clearly states the action (get) and resource (VERO report), and specifies retrieval by identifier. It is distinct from sibling tools like ebay_get_vero_report_items, but lacks context explaining what a VERO report is.

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 (e.g., ebay_get_vero_report_items) or prerequisites like first creating a report via ebay_create_vero_report.

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