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

Annotations already mark the tool destructiveHint=true, and the description adds significant behavioral context: existing escalations opened by the rule remain but are marked as belonging to a deleted rule, and the deletion cannot be undone from the API. This goes well beyond what annotations alone convey.

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?

Three short sentences each earn their place: the action, the side effect on existing escalations, and the confirmation requirement plus irreversibility. The most important behavioral consequence is front-loaded near the top.

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 simple tool with only one required integer parameter and no output schema, the description is complete. It states the action, the lingering effect on escalations, the user-confirmation requirement, and the irreversibility, giving an agent everything needed 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 single id parameter clearly described as 'Escalation rule id.' The description adds no additional parameter-level meaning, so the baseline of 3 applies because the schema already carries the semantic weight.

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 'Delete an escalation rule,' a specific verb and resource that is unambiguous. It is clearly distinguishable from sibling tools like create_escalation_rule, update_escalation_rule, get_escalation_rule, and list_escalation_rules.

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 a clear operational context: the tool is for deleting a rule, and it explicitly instructs the agent to 'Confirm with the user first.' It does not name an alternative tool or state when not to use it, but the precondition and the destructive nature make usage conditions clear.

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