ads_delete_ad

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

The word 'permanently' discloses irreversibility, which is useful. However, with no annotations, the description fails to mention role of the confirm parameter (likely to prevent accidental deletion), the behavior when confirm is false, or any permission requirements. This is a destructive operation and needs more behavioral disclosure.

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 short sentence with no fluff. It adequately states the core purpose, though it could include more detail without becoming verbose. It earns its place but is slightly under-specified in favor of brevity.

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 delete tool with no annotations, no output schema, and two parameters (one required, one with default), this description is incomplete. It doesn't explain the behavior of the confirm flag, possible errors, return format, or any consequences beyond 'permanently'. The agent would be left guessing about safe usage.

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 by explaining parameters. It mentions neither ad_id nor confirm. The confirm boolean's meaning (e.g., whether it's required to actually delete) is completely unaddressed. The description adds no value beyond the schema property 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 clearly states the action (delete), the resource (a single ad), and the scope (permanently). It effectively distinguishes from sibling tools like ads_pause_ad or ads_activate_ad, and the 'single ad' qualifier differentiates it from ads_delete_campaign or ads_delete_adset.

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?

No guidance is provided about when to use this tool versus alternatives. It doesn't mention that this is for permanent removal as opposed to pausing/adjusting, nor does it explain any prerequisites or the purpose of the confirm parameter. Sibling tools like ads_pause_ad exist, so explicit alternatives would be valuable.

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