meta_ads_catalogs_delete

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

With no annotations, the description fully discloses the destructive nature, cascading effects on products and DPA campaigns, non-reversibility, and the need for rollback logging. This goes far beyond a simple delete and provides critical safety information.

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 four sentences, each delivering essential information: the action, the return value, the destructive consequences, and the prerequisite/rollback guidance. It is front-loaded with the purpose and avoids unnecessary 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 destructive tool with no output schema and no annotations, this description covers purpose, effects, prerequisites, and rollback. It is remarkably complete for its length, addressing all critical decision-making needs.

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 100%, so the baseline is 3. The description does not add specific semantics for account_id or catalog_id beyond the schema, but the schema already documents them thoroughly, so no penalty.

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 tool 'Deletes a Product Catalog' with a specific verb and resource, and mentions the success flag. The name meta_ads_catalogs_delete further distinguishes it from sibling tools like create/get/list.

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?

It provides an explicit precondition: 'Always call meta_ads_catalogs_get first to check product_count and operator-confirm before calling this.' It also mentions using mureo_state_action_log_append for rollback, which gives context on when additional steps are needed. However, it does not explicitly state when not to use this tool or mention alternatives.

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