products_delete_product_collection

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

The description only says 'Delete', which aligns with the destructiveHint annotation but adds no additional behavioral context like irreversibility, cascading effects, or required permissions. With annotations already covering destructive and idempotent behavior, the description contributes nothing extra.

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, clear sentence that conveys the essential action without unnecessary words. It is appropriately concise for a straightforward delete operation and is well-structured.

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 tool with full schema coverage and annotations declaring destructive and idempotent behavior, the description is minimally adequate. However, it could be improved by mentioning consequences of deletion (e.g., what happens to associated data) or expected response, since there is no output schema.

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 coverage is 100%, so all three parameters are already documented in the input schema. The description does not add any additional meaning about how parameters interact or their significance, keeping this at the baseline score for high 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 'Delete Product Collection' clearly states a specific action and resource, distinguishing it from siblings like products_delete_product_by_id. However, it is minimal and doesn't elaborate on scope or exact behavior, so it falls slightly short of a perfect score.

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?

There is no guidance on when to use this tool versus alternatives such as deleting a product or price. No conditions, prerequisites, or exclusions are provided, leaving the agent to infer usage from the name alone.

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