Delete a Meta campaign / ad set / ad

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

Clearly states the action is irreversible and requires confirmation. Annotations already indicate destructive and non-read-only, but description adds crucial context about the confirm parameter and source of objectId.

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 convey action, objects, parameter hints, and alternative. Every sentence provides essential information without redundancy.

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?

Covers all critical aspects: purpose, prerequisites (objectId from list_meta_ads), confirmation requirement, irreversibility, and alternative for non-destructive pausing.

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?

Adds meaning beyond schema: explains objectId comes from list_meta_ads, adAccountId for auth/scope, and confirm is required and must be true. Schema coverage is 100%, but description enriches with usage context.

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 performs permanent deletion of campaigns, ad sets, or ads. It distinguishes from siblings like update_meta_object by contrasting deletion vs pausing.

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 tells when to use (permanent delete) and when not (use update_meta_object for pausing). Also advises to confirm with user first and set confirm:true.

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