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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds useful domain context that open escalations await a human answer, but says nothing about ordering, pagination, or whether resolved escalations are included. With annotations carrying the safety burden, this is adequate but thin.

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 short sentence with a clarifying parenthetical — front-loaded and waste-free. Brevity is fine here since the tool is trivial, though the space saved could have documented the parameter.

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, read-only list tool with no output schema, the description is minimally sufficient. However, it omits whether results default to all/open escalations and how the 'open' flag alters output, which an agent needs to call 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 0% on the single boolean 'open' parameter. The description mentions 'open ones' but never clarifies that 'open' is a filter parameter or what passing false returns. This is a real gap the description could have closed with a clause.

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?

Clear verb+resource: 'List escalations'. The parenthetical adds domain context about what open escalations mean. It doesn't explicitly distinguish itself from sibling 'resolve_escalation', but the list-vs-resolve distinction is reasonably inferable.

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?

No guidance on when to call this versus 'resolve_escalation' or other listing siblings. There is no statement of prerequisites or context that would trigger a retrieval. Usage is left entirely to inference from the name.

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