ebay_delete_product_compatibility

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

The description only states the action without detailing behavioral traits. It does not specify whether it deletes all compatibility entries for the SKU, whether it is idempotent, or what happens if no compatibility exists. Since no annotations are provided, the description should compensate, but it does not.

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 extraneous information. It is efficiently front-loaded, though slightly more context could be added without losing 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 simplicity (1 parameter, no output schema, no annotations), the description is too brief. It does not explain the scope of deletion, effects, or error conditions, leaving significant gaps for an AI agent.

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?

There is only one parameter, 'sku', which is already described in the schema as 'The seller-defined SKU'. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate given the 100% schema coverage.

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) and the resource (product compatibility for an inventory item). It is specific and distinct from sibling tools like 'create_or_replace_product_compatibility' and 'get_product_compatibilities'.

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 is provided on when to use this tool versus alternatives, such as batch deletions or updates. There is no mention of prerequisites or conditions, leaving the agent to infer usage context.

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