ebay_create_report_task

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

The description mentions the task is asynchronous and generated in the background, but lacks details on what the response contains (e.g., task ID), typical processing time, error conditions, or that the agent should subsequently use get_report_task to check status. With no annotations, the description carries the burden of disclosure and falls short.

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 only two sentences and avoids unnecessary detail, but could be slightly expanded to include critical workflow context without becoming verbose.

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 tool with a nested object and no output schema, the description omits key usage context such as the async workflow, expected response format, and how to handle the task afterwards. The schema covers parameters well, but the description doesn't bridge the gap to practical usage.

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, so the schema already explains each parameter. The description adds no extra meaning beyond what's in the schema, placing it at the baseline of 3.

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 creates an asynchronous report generation task, which distinguishes it from tools that retrieve or delete reports. However, it doesn't specify the types of reports or how it differs from other report creation tools like ebay_create_vero_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 provides no guidance on when to use this tool versus alternatives like ebay_get_report_task or ebay_get_report. It doesn't mention that the task must be polled or that reports are generated asynchronously, leaving the agent without context for proper workflow.

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