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 structurally. The description adds genuine value beyond that by explaining the blast radius (rules are inert config; deleting unfired config moves no candidates), which tells the agent why this destructive call is low-risk. It omits permissions requirements and the fact that request_id serves as an idempotency key.

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 tight sentences, front-loaded with the action and then the risk rationale; nothing redundant. The parenthetical "no approval preview→bind" is notation-dense and slightly harder to parse than plain prose, but it earns its space.

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 mutation with no output schema, the description covers purpose and blast radius, and annotations cover idempotency/destructiveness. It is still thin on parameter semantics (especially request_id) and error/failure behavior, so it is adequate but with visible gaps.

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 two parameters, so the schema names rule_id and request_id without explaining either. The description adds no parameter meaning at all — nothing about rule_id format or that request_id is an idempotency/replay key — leaving the burden unfulfilled despite the low coverage.

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 opens with a specific verb+resource ("Delete an automation rule") and immediately scopes it as a plain delete rather than the preview→bind pattern used by sibling operations, so an agent can distinguish it from yardstick_automation_rules_preview, _preview_rule, and the bind-style siblings without opening the 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?

By stating "Plain delete (no approval preview→bind)" it clarifies the condition under which this direct tool is used instead of a preview/approval flow, which is meaningful routing guidance in this sibling set. It stops short of explicitly naming the alternative tools or stating when deletion is inappropriate, so it is clear context but not a full when/when-not rule.

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