ebay_delete_inventory_item

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

No annotations are provided. The description adds the OAuth scope requirement but does not disclose important behavioral traits like whether deletion is irreversible, whether it fails if the item is associated with an active listing, or any other side effects.

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, front-loading the action and parameter. Every sentence adds value—the first sentence states the purpose, the second adds the required scope. No fluff.

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 sufficient. However, it lacks context about potential failure reasons or consequences, which would be beneficial given the lack of annotations.

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 description coverage is 100% for the single parameter 'sku', which is adequately described as 'The seller-defined SKU'. The description does not add further meaning beyond the schema, so 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 the action 'Delete an inventory item' and specifies the unique identifier 'by SKU'. This clearly distinguishes it from sibling tools like create, replace, or get inventory items.

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 mentions required OAuth scope but does not provide guidance on when to use this tool versus alternatives such as bulk delete or deleting inventory item groups. No exclusion criteria or prerequisites are stated.

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