herdr_pane_wait_output

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is known. The description adds little beyond that: it doesn't explain what happens on timeout (does it fail? return partial output?), whether it blocks or polls, or how the match is evaluated across the buffer. For a waiting/blocking operation, these are important behavioral details.

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 that front-loads the core action and scope. No waste, no redundancy.

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?

The tool has 6 parameters (1 required), no output schema, and annotations that cover safety. The description states the core purpose but omits critical operational details for a wait tool: timeout behavior, blocking vs polling, and what constitutes a match (entire buffer vs recent lines). For a tool with this complexity, it is minimally complete but leaves meaningful gaps.

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 coverage is 100%, so the schema documents all six parameters, including enum for source and defaults. The description adds no parameter-level meaning beyond the schema. With full schema coverage, 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?

Clear verb+resource: 'wait until a pane's output matches'. States the resource (pane output) and the trigger condition (text or regex). However, it doesn't differentiate from the sibling herdr_pane_read or herdr_agent_wait, which could also relate to waiting for output.

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 alternatives mentioned. Given siblings like herdr_pane_read and herdr_agent_wait, an agent cannot tell from the description whether to poll with this or use another tool. The description says what it does but not when to choose it.

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