stdbuf

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

The description states the tool 'Executes as a subprocess' and 'captures bounded stdout/stderr' which are write/mutate operations, but annotations include readOnlyHint: true, which claims no side effects. This is a direct contradiction. The description does not align with 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 description is concise, starting with the core purpose and then providing additional details in logical order. Every sentence adds value, and it is well-organized without 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?

Given the complexity (7 parameters, no output schema), the description covers key aspects: buffering modes, subprocess execution, output capture, timeout, and dry run. It misses details on how outputs are returned, but overall it is sufficiently complete for the tool's purpose.

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% (all 7 parameters described). The description adds extra context beyond schema, such as explaining buffering modes (0, L, byte size), default behavior, and the purpose of dry_run. This enhances understanding.

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 verb 'Run a command' and the resource 'controlled stdout/stderr/stdin buffering'. It distinguishes from sibling tools like nice and timeout by specifying what it is not for. The purpose is unambiguous.

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 description explicitly states when to use this tool ('diagnose buffering-related output delays or ordering issues in pipelines') and when not to use it ('Not for CPU priority control' and 'Not for time-bounded execution') with direct references to alternatives (nice, timeout).

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