ebay_create_vero_report

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool 'creates' a report, implying a mutating action, but does not elaborate on potential side effects, authorization requirements, rate limits, or output structure. The behavior is minimally described.

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 two sentences long, front-loaded with the core action and purpose, and includes essential context (VeRO Program). No redundant or extraneous information is present.

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?

For a creation tool, the description adequately conveys the high-level functionality and program context. However, it lacks details about the response format, error handling, and any prerequisites (e.g., being a VeRO participant). Given no output schema and no annotations, a bit more context would be beneficial, but it is still fairly complete.

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% coverage with descriptions for the main object, but the tool description adds no additional explanation of the parameters. The schema already describes 'reportData' as containing item details and IP violation information. Thus the description provides no added semantic value beyond 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 verb 'Create', the resource 'VERO report', and the specific purpose 'report intellectual property infringement'. It also places the tool within the VeRO Program, distinguishing it from other VERO-related tools like 'ebay_get_vero_reason_codes' and 'ebay_get_vero_report' which are read operations.

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 indicates who can use it ('rights owners') and for what purpose, but does not provide explicit guidance on when to use this tool versus alternatives such as 'ebay_create_complaint' or other reporting tools. No prerequisites or exclusions are mentioned.

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