meta_ads_catalogs_delete

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

With no annotations, description fully covers destructive nature, cascade to products and DPA campaigns, and reversibility constraints, leaving no behavioral ambiguity.

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?

Three dense sentences: purpose, side effects, prerequisites. No fluff, every sentence earns its place, front-loaded with core purpose.

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 delete tool with 2 params and no output schema, description fully covers behavior, prerequisites, side effects, and return value (success flag).

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 covers both parameters with detailed descriptions (100% coverage). Description adds no extra parameter info beyond schema, so baseline 3.

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?

Clearly states verb (Deletes) and resource (Product Catalog), and distinguishes it from sibling tools like create, get, list, and rollback_apply.

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?

Explicitly calls out prerequisite (check product_count with catalogs_get and operator-confirm), warns about cascading effects, and explains reversibility conditions via rollback_apply.

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