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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the blast radius is known. The description adds the 'Admin only' auth requirement, which is real added context, but says nothing about the confirm/confirm_live/dry_run safety flags that are present in the schema.

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 front-loaded sentences with zero filler. Brevity is a virtue here, though the extreme terseness is arguably under-specification rather than economy given the tool's complexity.

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 tool with 33 undocumented parameters, the definition provides only an auth note. The output schema may cover returns, but the input surface — which fields identify the rule and which are safety switches — is completely unaddressed.

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?

33 parameters at 0% schema description coverage, and the description mentions none of them. An agent has no way to know whether rule_id, name, or scope identifies the target rule, nor what confirm, dry_run, or confirm_live do. The description fails the compensation burden entirely.

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+resource ('Delete an ads alert rule'), which separates it from deletion siblings covering SEO alert rules and automation rules. It stops short of naming those siblings, but the resource is unambiguous.

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?

'Admin only' is a permission gate, not usage guidance. The description never says when to delete versus upsert (automate_upsert_alert_rule) or how it relates to list_alert_rules, nor does it warn that this is irreversible.

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