ebay_delete_report_task

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

The description discloses the action (delete) and the precondition (only completed or failed tasks). However, it does not mention whether deletion is irreversible or if there are any side effects. Given no annotations, the description carries the burden, and it provides adequate but minimal transparency.

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 very concise, consisting of two sentences. It is front-loaded with the action and constraint, with no unnecessary words. Every sentence earns its place.

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 simplicity of the tool (one parameter, no output schema, no nested objects), the description is complete enough. It covers the purpose and a key constraint. It could mention if deletion is permanent, but is adequate for a basic delete operation.

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 is fully described (100% coverage) and the description for the parameter 'reportTaskId' is 'Report Task ID', which is clear. The tool description adds nothing beyond the schema, so a baseline score of 3 is appropriate.

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 that the tool deletes a report task, with the specific condition that only completed or failed tasks can be deleted. This provides a specific verb and resource, and distinguishes from other tools by adding the constraint.

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 tells when to use the tool (delete a report task) and when not to (only if completed or failed), implying that tasks in other states should not be deleted. It does not explicitly mention alternatives but the constraint is clear.

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