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

Annotations already supply destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value on top: the hint that deletion is not recoverable and that a reversible alternative exists. It does not disclose side effects on any dependents of the rule, but that is a minor gap given the annotation coverage.

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, zero waste, with the core action front-loaded ahead of the alternative-tool guidance.

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 single-parameter destructive mutation with no output schema and annotations covering safety, the description gives purpose plus the key decision cue. It omits what happens if the ID is invalid or whether any related state is affected, but nothing essential for correct invocation is missing.

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% for the single parameter, so the description must carry the burden of explaining automation_rule_id, and it says nothing about it. The parameter is a self-evident integer identifier with a documented type and minimum in the schema, so the omission is tolerable, but no added semantic value is provided.

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 states a specific verb ('Delete') and resource ('automation rule') and immediately contrasts itself with the sibling toggle_automation_rule. An agent can distinguish it from the many other delete_* tools without opening any schema.

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?

It names an explicit alternative (toggle_automation_rule) and the condition that selects it ('when the administrator may want it back'), which also implies the permanence of deletion. It stops short of stating prerequisites (e.g., rule must exist, required permissions) or other when-not conditions, so it is clear context rather than a complete decision rule.

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