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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this is a blocking wait for a pattern, but does not disclose timeout/partial-output semantics (left to the schema) or how it differs behaviorally from a plain read. With annotations carrying the safety load, this is adequate but not rich.

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 with two illustrative examples and zero filler. Every clause earns its place and the usage trigger comes first.

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?

Return values need not be explained since an output schema exists, and annotations cover safety, so the remaining burden is routing and blocking semantics. The description conveys the core intent well but leaves the read-vs-wait sibling distinction implicit, a minor gap for a 4-param tool with full schema coverage.

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%, so pid, device, pattern and timeout_ms are all documented in the schema, including the 10000ms default and the partial-output-on-timeout behavior. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 verb+resource+scope: wait until a running command prints a specific pattern. It is clear what the tool does, but it never names or contrasts with the nearest siblings read_process_output (non-blocking read) or wait_for_ui, so an agent must infer the distinction from the name alone.

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?

It gives a clear when-to-use condition ('wait until a running command prints something specific') with concrete examples (readiness line, failing test name). There is no explicit when-not guidance or named alternative for the immediate-read case, so it stops short of the top score.

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