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 safety profile is covered. The description adds one genuinely new behavioral fact, the Admin plan and Starter+ tier requirement, which the annotations do not carry, but it omits the likely confirmation/dry-run flow suggested by the confirm, confirm_live and dry_run parameters.

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, front-loaded sentences with no filler. It is efficient, but the brevity is partly under-specification rather than disciplined concision given the complexity of the operation.

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, non-required parameters and 0% schema coverage, the description supplies only a purpose and a plan gate. It says nothing about identifying the target rule, the confirmation mechanics, or the intended invocation path, leaving the agent without what it needs to call this safely.

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% across 33 parameters and the description offers no parameter meaning at all. An agent gets no help identifying which field (e.g., rule_id, name, or scope) actually targets the rule, and no guidance on the many null-defaulted fields, so the description fails to compensate for the coverage gap.

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 ('Delete') and a specific resource ('SEO/AEO alert rule'), which lets an agent distinguish it from automate_delete_alert_rule and automate_delete_automation_rule by resource type. However, it never clarifies what distinguishes an SEO/AEO alert rule from a plain alert rule, so the differentiation still leans on the tool name.

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 + Starter+' is a plan/permission gate, not usage guidance. The description never says when this tool should be chosen over the sibling delete tools, nor does it mention the confirm/dry_run path that a 33-parameter destructive operation clearly implies.

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