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

The annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds the useful semantic outcome that the case leaves automated handling and goes to a human, but it does not say what state the exception lands in, whether repeating the call creates duplicate escalations, or whether it can be undone.

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?

A single front-loaded sentence that states the action, the recipient, and the triggering condition with zero filler. Nothing could be trimmed without losing the rationale clause.

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, non-idempotent, two-parameter mutation with no output schema and 0% parameter coverage, the description is too thin. It omits parameter meaning and the observable result of escalation, so an agent cannot confirm what happens to the exception after the call.

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%, so both exception_id and reason are undocumented in the schema, and the description supplies nothing about their format or content. It never hints at what a valid exception_id looks like or what a useful reason string should contain, leaving the burden entirely unmet.

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 action and object: routing an exception to a human. It implicitly differentiates from resolve_exception by framing this as the path taken when policy cannot be applied, but it never names the sibling it displaces, so an agent must infer the split.

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?

"because the policy cannot be applied" gives an implied precondition for use, which is more than nothing, but there is no explicit when-not guidance and no named alternative such as resolve_exception or reject_invoice for cases where policy does apply.

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