ebay_delete_report_task

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

Annotations already declare destructiveHint: true, and the description's 'Delete' matches this. The description adds no additional context beyond the annotation—e.g., whether deletion is permanent, impacts on associated reports, or requires specific permissions—so it carries minimal extra value beyond the structured metadata.

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, concise sentence with no filler. It immediately states the action and resource, making it highly efficient and front-loaded.

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 simple delete operation with one parameter and no output schema, the description is functionally adequate. It does not mention prerequisites, side effects, or response behavior, but given the tool's low complexity and the annotation covering destructive intent, the gaps are not severe.

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 describes the sole parameter 'reportTaskId' as 'reportTaskId required endpoint parameter', which is minimal but present. The description itself adds no further meaning. Since schema coverage is 100%, the baseline of 3 applies; the description neither helps nor hinders parameter understanding.

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 'Delete' and the resource 'report task', which distinguishes it from related siblings like ebay_get_report_task, ebay_create_report_task, and ebay_get_report_tasks. It does not mention any scope or qualifiers, but the action and target are unambiguous.

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. However, the action is self-evident—you delete a report task when it is no longer needed—and there are no competing delete-report-task tools among siblings, so the need for explicit usage guidance is limited.

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