meta_ads_products_delete

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

With no annotations provided, the description fully discloses destructive behavior: it is irreversible, affects DPA/Collection ads on the next serve cycle, and warns about new product_id assignment on re-add. It even suggests a rollback mechanism. This is comprehensive behavioral disclosure beyond the structured fields.

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 front-loaded with the main action and returns value, then provides necessary warnings and alternatives. Every sentence earns its place—there is no fluff or redundancy. Length is appropriate for the destructiveness of the operation.

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?

The description covers the tool's effect (deletes a product), return value (success flag), side effects (ads skip product), reversibility (not automatic), rollback strategy (mureo_state_action_log_append), and an alternative approach. For a destructive tool with no output schema and no annotations, this is exceptionally complete.

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%, so baseline is 3. The description adds value by explaining the consequence of using product_id with the same retailer_id (new Meta product_id on re-add), which deepens understanding of the product_id parameter beyond its simple schema description.

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 verb and resource: 'Deletes a single catalog product.' It distinguishes from siblings like meta_ads_products_update and meta_ads_products_add. The scope is precise and unambiguous.

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?

The description provides explicit guidance on when to use this tool and when to avoid it. It names a specific alternative for temporary suppression: 'meta_ads_products_update with availability="out of stock"'. It also advises recording state for rollback, which is contextual usage guidance.

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