Delete Ad Set

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

The annotations already provide destructiveHint=true and idempotentHint=false. The description adds the word 'permanently', which reinforces irreversibility, but it does not disclose potential side effects such as what happens to ads within the ad set, permission requirements, or whether deletion can be undone. This is acceptable given the strong annotation signal, but the description itself adds limited behavioral context.

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: one sentence for the action and one short arg block. It front-loads the core purpose and contains no filler or redundant information.

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?

Given the tool's low complexity, one required parameter, and annotations that already flag destructive behavior, the description is nearly complete. It clearly states the action and the parameter. It does not describe the return value or cascade effects on child entities, but for a one-parameter delete operation this is a minor 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 carries the burden of explaining adset_id. It does so by labeling it as 'Ad set ID to delete', which adds meaningful semantic context beyond the bare string type in the schema. It could include a format example, but for a single simple parameter this is sufficient.

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 ('Deletes'), a clear resource ('an ad set'), and an important qualifier ('permanently'). This clearly distinguishes it from sibling delete tools like meta_delete_ad, meta_delete_campaign, and meta_delete_post.

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 makes the intended usage obvious: use this tool when an ad set needs to be permanently deleted. It does not explicitly name alternatives or exclusion conditions, but the resource-specific naming and description make confusion with other delete tools unlikely.

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