Delete product catalog

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description earns credit for disclosing cascade behavior beyond the annotations: deleting the catalog also removes its feeds, sets and products. It does not state permission requirements or whether the action can be undone.

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?

One sentence, front-loaded with the verb and permanence warning, conveying both the target and the blast radius without waste.

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 one-parameter destructive tool with no output schema, the description covers the essential risk information (irreversibility plus cascade scope). It stops short of prerequisites such as required permissions or confirmation steps, but an agent can call it correctly with what is given.

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 0% and the description says nothing about catalog_id, so no meaning is added beyond the schema's type/minLength. The single parameter is self-evident by name, which keeps this at the baseline rather than lower.

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?

States a specific verb ('Permanently delete') and resource ('product catalog'), and adds the cascade scope (feeds, sets, products) that separates it from sibling deletes like reddit_ads_delete_product_feed, reddit_ads_delete_product_set and reddit_ads_delete_products. It never names those siblings explicitly, so differentiation is implied rather than spelled out.

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 when-to-use or when-not-to-use guidance and no mention of the narrower deletion siblings (delete_products, delete_product_feed, delete_product_set) that an agent might prefer. The cascade scope hints at the tool's role, but the agent must infer that this is the wholesale option.

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