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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is carried by structured data. The description adds the dry-run/preview semantics, which is genuinely useful and not in the annotations, but it omits cascade effects (does deleting an ad set remove its ads?) and what confirm=true triggers.

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 sentences with zero filler and the action stated first. It is telegraphic rather than padded, though the fragment 'confirm=false = preview' is terse enough to risk ambiguity about what preview returns.

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/idempotency profile. Still, for a high-blast-radius delete, the absence of any note on cascade effects or irreversibility leaves a meaningful gap.

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 explains the non-obvious confirm flag's dual preview/execute role. It leaves adset_id and account_id undocumented, though both are self-describing by name and type.

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 and resource ('Deletes a Meta ad set'), so the action is unambiguous. It does not explicitly distinguish itself from the numerous sibling delete tools (delete_meta_ad, delete_meta_campaign, delete_meta_audience), though the resource name does most of that work implicitly.

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?

'confirm=false = preview' gives real conditional guidance on how to invoke it safely, which is above the bare minimum. It still says nothing about prerequisites (e.g., whether dependent ads must be removed first) or when deletion is preferable to pausing via update_meta_adset.

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