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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context by revealing the confirm=false preview/dry-run mode, which annotations do not expose, but it omits whether deletion is permanent or recoverable and whether scoped permissions are required.

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 short fragments, front-loaded with the action and immediately followed by the mode switch — nothing wasted. It is arguably clipped to the point of dropping prerequisites, but it is efficiently structured.

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?

An output schema exists, so return values need not be described, and annotations carry the destructive/non-idempotent profile. The description covers the one non-obvious behavior (preview via confirm=false); it is slightly thin on consequences of a real delete but adequate for this tool's complexity.

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 compensate. It does explain the pivotal 'confirm' parameter semantics (false = preview), which is not in the schema, but account_id and ad_id are left wholly undocumented even though they are required identifiers.

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?

States a specific verb (Deletes) and resource (a Meta ad), which cleanly separates it from delete_meta_adset, delete_meta_campaign, and delete_meta_audience by name alone. It does not explicitly contrast itself with those siblings, but the resource is 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 preview mode ('confirm=false = preview') gives the agent a real usage cue, effectively describing the safe dry-run path. However, it never states when to prefer this over alternatives like pausing via update_ad_status or deleting a parent campaign, so guidance is implied rather than explicit.

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