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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful context (workspace-scoped, browser-lane, intended for customer-owned agents) but says nothing about pagination, result volume, or ordering, which is the kind of detail that would push this higher.

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 well-formed sentence with the resource front-loaded and no filler. Every clause earns its place.

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 two-parameter, optional-filter list tool with full schema coverage and annotations covering safety, the description is nearly complete. Leaving "browser-lane" undefined and not mentioning the available filters keeps it from a 5.

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% (run_id and status are both documented, with status enum values), so the schema carries parameter meaning. The description adds nothing about the two optional filters, so baseline 3 is appropriate.

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?

States a specific verb+resource ("List browser-lane escalations") and scopes it to the workspace, which distinguishes it reasonably well from action siblings like claim_escalation and resolve_escalation. It stops short of explicitly contrasting itself with those siblings, but an agent can infer read vs. act.

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 clause "so a customer-owned agent can resolve them" implies the intended workflow (read before acting) but never states when to use this versus claim_escalation, resolve_escalation, or abandon_escalation, nor any exclusions. Usage is only implied, not specified.

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