delete_ads

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

Discloses irreversibility, stats loss, and dry-run behavior via confirm parameter. No annotations provided, so description bears full burden. Could mention effect on ad groups.

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?

Dense, well-structured with warning, alternative, and Args block. No redundant sentences, front-loaded purpose.

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?

Covers all essential aspects for a simple delete tool with two parameters and no output schema: purpose, side effects, alternative, parameter semantics.

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?

With 0% schema coverage, description explains both parameters: ad_ids as list of IDs, confirm as toggle for dry-run. Adds value beyond type info but omits confirm default (false).

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?

Clearly states 'Permanently delete ads' with a specific verb and resource. Distinguished from sibling tools like 'archive_campaigns' and 'delete_keywords'.

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?

Explicitly suggests archiving as alternative when history needs to be preserved. Does not cover other exclusions or when-not-to-use cases.

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