Delete products

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is fully covered by structured data. The description adds the batch cap of 1000 and the catalog scoping, but says nothing about irreversibility, confirmation requirements, or partial-failure behavior beyond what the annotation implies.

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?

A single front-loaded sentence with zero filler. The action, scope, keying field, and limit are all packed efficiently with no wasted words.

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 two-parameter destructive delete with annotations carrying the safety profile and no output schema, the description is largely complete. It could go further in noting irreversibility or recovery, but nothing essential for correct invocation is missing.

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 50%: 'data' is documented as 'Product IDs' while 'catalog_id' has no description. The description reinforces that deletion targets product IDs within a catalog, which maps both parameters, but adds no format or syntax detail beyond the schema. Baseline 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 states a specific verb (delete), resource (products), scope (from a catalog), and method (by product ID), plus a batch limit of 1000. It is very clear but does not explicitly differentiate itself from related siblings such as reddit_ads_upsert_products, relying on the reader to infer the distinction from the verb.

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?

Usage is implied by the destructive verb 'delete' within a catalog context, so an agent can reasonably infer when it applies. However, there is no explicit when-to-use guidance or reference to the alternative reddit_ads_upsert_products (which adds/updates products), leaving the delete-vs-upsert decision unstated.

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