terminal.wait_stable

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

The description discloses that a snapshot is returned even on timeout with timedOut=true. This adds context beyond the schema. However, it does not explain what 'stable' means or if the tool blocks, though that is implied.

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 description is a single sentence that conveys the core purpose and a key behavioral trait. No wasted words.

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?

Given the simple nature of the tool and the full schema coverage, the description is sufficient. It explains the timeout behavior, which is critical for correct usage.

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?

All parameters have schema descriptions, so the description adds no extra meaning. The description does not elaborate on the parameters beyond what the schema provides, meeting the baseline.

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 clearly states the tool waits for terminal stability and describes the timeout behavior. It distinguishes itself from siblings like terminal.snapshot and terminal.wait_for_text by focusing on stability rather than capturing state or specific text.

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 explicit guidance on when to use this tool versus alternatives. It is implied for ensuring stability before further interactions, but lacks exclusion criteria or references to siblings like terminal.wait_for_text.

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