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

Although annotations already mark the tool as destructive, the description adds meaningful behavioral context: deletion is permanent and irreversible. It also discloses bulk execution support via ad_ids, which goes beyond the structured annotations.

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 extremely concise, front-loads the core message, and adds only the high-value detail about bulk support. Every sentence earns its place with no wasted text.

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 destructive nature, irreversibility, and bulk capability, which is reasonable for a delete tool with strong annotations. However, the lack of parameter semantics and absence of any guidance on batch vs single deletion leaves the description incomplete for a fully informed agent.

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 for parameter ambiguity. It only explains ad_ids for batching and does not clarify the relationship between ad_id and ad_ids, nor the purpose of auth_account. This leaves key invocation semantics underspecified.

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 identifies the action ('Permanently delete') and the resource ('a Meta Ads ad'), making the tool's purpose unmistakable. It also differentiates from sibling delete tools by naming the 'ad' resource rather than adset, campaign, or audience.

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 gives no guidance on when to use this tool over sibling delete tools, nor when not to use it. The bulk-support note hints at one usage scenario, but there is no explicit direction about prerequisites, alternatives, or exclusion cases.

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