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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds real value beyond that by disclosing the guard mechanism: confirmation requires both confirm=true and a matching confirm_name, which is exactly the context an agent needs before an irreversible delete. It stops short of saying what failure looks like on a name mismatch.

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 sentences with zero filler, the destructive action stated first and the prerequisite sequence second. Every clause carries 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?

For a destructive, multi-account tool with no output schema, the description covers the confirmation protocol but leaves the preview step undefined — an agent does not know whether previewing means calling this tool without confirm, or calling meta_rules. That single omission is the difference between safe and accidental deletion.

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 coverage is 50%, and the description does compensate for the undocumented parameters by explaining confirm and confirm_name's matching constraint, and implying rule_id identifies the target. However, folder, account, and language get nothing beyond the schema, and 'rule name' is never tied to a discovery source.

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?

Specific verb+resource: 'Delete an automated rule', which is unambiguous in this ecosystem and distinct from meta_remove (generic entity removal) or meta_create_rule. It does not explicitly name those siblings, so an agent must infer the boundary from the noun 'rule' alone.

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?

'Preview first, then confirm=true' implies a two-step flow, but never says how to preview — whether a bare call acts as a dry-run, or whether another tool (meta_rules) must be consulted first. There is no guidance on exclusions or on what to do if the rule is active.

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