ebay_delete_inventory_item

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

No annotations are provided, so the description carries the burden of disclosing behavior. It adds the OAuth scope requirement, which is useful, but does not explain the consequences of deletion (e.g., irreversibility, impact on offers or listings, data retention). For a mutation tool, this is insufficient.

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 contains two concise sentences: one for the core action and one for the required OAuth scope. No extraneous information, and the most critical information is 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?

Given the simplicity of the tool (one parameter, no output schema), the description covers the basic action but lacks details on error handling, side effects, or dependencies. The OAuth scope adds context, but completeness is still only adequate.

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 already describes the 'sku' parameter with 100% coverage. The description does not add additional semantic meaning 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 explicitly states 'Delete an inventory item by SKU', clearly identifying the action (delete), resource (inventory item), and identifier (SKU). This sufficiently distinguishes from sibling tools like 'ebay_delete_inventory_item_group' and 'ebay_bulk_delete_ads_by_inventory_reference'.

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 only mentions the required OAuth scope, which is an authentication constraint. It provides no guidance on when to use this tool versus alternatives (e.g., bulk delete operations), prerequisites, or scenarios where deletion is appropriate.

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