ebay_create_report_task

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

Discloses asynchronous background generation, but with no annotations, the description should provide more (e.g., needing to poll for completion, potential failure modes). Lacks crucial behavioral details for a creation tool.

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?

Two sentences, front-loaded with action. No wasted words, though could be slightly more informative without violating conciseness.

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 nested input schema and no output schema, the description is incomplete. It does not explain what the tool returns or how to use the result (e.g., poll with ebay_get_report_task).

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?

Schema coverage is 100%, so description adds no extra meaning. Baseline 3 as it does not contradict or expand on schema descriptions.

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?

Clearly states creating an asynchronous report generation task. The verb 'create' and resource 'report task' are specific, but it does not explicitly differentiate from sibling tools like ebay_create_vero_report or ebay_get_report_task, relying on the name and context.

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?

No guidance on when to use this tool versus alternatives (e.g., ebay_create_vero_report, ebay_get_report). No context on prerequisites or typical use cases.

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