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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds a useful detail about the 'say' field containing a ready-to-read summary, which is genuinely beyond the annotations. But it does not explain ordering, pagination, or what an empty result means.

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, front-loaded with the identifying phrase, no filler. The third sentence about 'say' is useful and earns its place. Slightly fragmented as prose, but efficient.

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 zero-param read-only list with no output schema, the description gives the gist and the 'say' summary location, which is helpful. However, without an output schema it should say more about the shape of the returned entries (fields an agent will see, ordering, whether empty is possible) and route to resolve_escalation for follow-up.

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?

There are zero parameters, so the baseline is 4; the schema is empty and there is nothing for the description to clarify or compensate for. No parameter-related claims are made or needed.

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 title and description gesture at the resource ('Applications that stopped and need the person') and the name list_escalations implies listing, but the description never states a clear verb for what the tool does. The examples (new questions, human check, failed send) add color but don't sharpen the purpose into an action statement. Sibling tools like resolve_escalation make the distinction inferable, but the definition itself doesn't articulate the list-vs-resolve boundary.

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 when-to-use guidance, no mention of the closely related sibling resolve_escalation, and no condition that tells an agent when to reach for this tool versus application_progress or get_tracker. The description just describes what escalations are, not when to call this tool.

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