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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the basic destruction profile. The description adds valuable non-obvious side effects: 'stop applying its badge' and 'escalation rules that reference the badge will no longer match', plus the requirement to confirm with the user. This goes beyond the structured data.

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 sentences with no filler: the first states the core action and immediate effect, the second adds the user-confirmation requirement and a critical consequence. Every sentence earns its place, and the action is front-loaded.

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 one-parameter delete tool, the description explains the effect (stops applying badge, escalation rules stop matching) and the necessary user confirmation. It doesn't discuss return values, but the annotations cover idempotency and destructiveness, so an agent has enough to invoke it correctly.

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 100%, with the 'id' parameter already described as 'Badge rule id.' The description does not add further parameter-level detail, so the baseline score of 3 applies; it doesn't harm but also doesn't enrich beyond the schema.

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 uses a specific verb and resource: 'Delete a badge rule', which clearly distinguishes it from siblings like update_badge_rule, create_badge_rule, and delete_escalation_rule. The added clause 'stop applying its badge' further clarifies the concrete effect, leaving no ambiguity about what the tool does.

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?

The description gives strong contextual guidance: it instructs the agent to confirm with the user first and warns that escalation rules referencing the badge will no longer match. It doesn't explicitly mention alternative tools or when-not-to-use conditions, but the context is sufficiently clear for an agent to decide correctly.

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