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

With annotations already declaring destructiveHint=true and readOnlyHint=false, the description adds useful context beyond the structured fields: reporting data remains readable in Meta, and confirm=false provides a safe preview. It does not mention permissions or irreversibility, but the core destructive behavior is well supplemented.

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 two compact sentences, front-loads the operation, and then adds the most important behavioral caveats. Every phrase earns its place 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?

For a destructive operation with annotations covering safety hints and an output schema covering return values, the description provides the essential behavioral context: deletion scope, retained reporting data, and preview mode. The main gap is parameter-level detail, but the required IDs are largely self-explanatory.

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 0%, so the description must carry parameter meaning. It explains only confirm=false as preview mode, while the two required parameters account_id and campaign_id receive no added semantics beyond their names.

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 states a specific verb and resource: deleting a Meta campaign. It distinguishes the target from sibling delete tools such as delete_meta_ad, delete_meta_adset, and delete_meta_audience by naming the entity type directly.

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 implies use when a Meta campaign should be deleted and explains the confirm=false preview mode. However, it gives no explicit when-to-use guidance versus alternatives like pause_campaign or update_meta_campaign, and names no exclusions.

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