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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false — they say nothing about content or routing — and the description fills that vacuum richly: synthetic orphan rows, server-derived task_retry_available, exact routing per escalation kind, and the legacy-ui-review vs. autonomy-ladder field difference. The one gap is that it never reconciles its read-oriented framing with the non-read-only, non-idempotent annotations.

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?

The scoping distinction is correctly front-loaded, but the remainder is one dense paragraph that packs row fields, synthetic-row semantics, next_tool routing, and two mode-dependent behaviors into undifferentiated prose. It is informative but hard to scan, and multiple clauses could be split or trimmed.

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?

Detailed enough that an agent knows what each row contains, what the synthetic rows mean, and which follow-up tool a row routes to, including the requeue_for_review task_id caveat. Since an output schema exists, the heavy return-field exposition is partly redundant, but the routing semantics it adds are not covered anywhere else.

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% for the single required project_id, and the description only references it obliquely through the `orphan:<project_id>` synthetic row format; it never says how to obtain or scope it. With one parameter and no schema documentation, more was expected than what is given.

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?

Opens with a concrete, specific framing: 'See what the work is stuck on and waiting for a human decision about,' which is unmistakably about listing escalations. It also explicitly contrasts with the closest sibling: '`project_status` only COUNTS open escalations; this returns each one' — an agent can distinguish the two without opening either schema.

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?

Gives a clear selection rule against project_status (counts vs. per-row detail) and names many downstream alternatives in the next_tool routing (retry_blocked_task, rearm_roadmap_item, requeue_for_review, answer_planning_question, resolve_escalation). It does not state exclusions such as when not to call this at all, so it falls short of the top mark.

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