meta_ads_catalogs_delete

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

Without annotations, description carries full burden. It discloses destructive cascading behavior, impact on products and DPA campaigns, and conditions for reversal via rollback_apply. Missing authentication or rate limit info, but sufficient for a delete operation.

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?

Two sentences, front-loaded with main action. The second sentence is somewhat long but packs necessary warnings. Efficient overall.

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?

No output schema, but description mentions return of success flag. Covers safety instruction and reversal path. For a destructive tool, the description adequately addresses completeness.

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%. Description adds useful context for account_id (optional, fallback, format) but catalog_id is just 'Catalog ID to delete.' No additional semantics beyond schema, but meets baseline.

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 'Deletes a Product Catalog' and mentions returns a success flag. It distinguishes from sibling tools like create, get, list by specifying the destructive action.

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?

Provides explicit instruction: 'Always call meta_ads_catalogs_get first to check product_count and operator-confirm before calling this.' It implies when to use (after verification) and warns of cascading effects, but does not name an alternative tool.

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