stdbuf

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

Description adds that it executes as a subprocess, captures bounded output, and enforces a safety timeout. Annotations only provide destructiveHint=true, which is consistent. No contradiction.

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?

Compact, front-loaded, no fluff. Each sentence adds value. Well-organized into purpose, details, exclusions.

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?

Covers purpose, usage, behavioral traits, and parameter context. No output schema is acceptable. Complete enough for agent decision-making.

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% with parameter descriptions, but description adds usage context (e.g., 'Use --dry_run to preview', 'Defaults to system buffering'). Reinforces without repetition.

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 runs a command with controlled buffering for stdout/stderr/stdin, specifying modes (0, L, byte size). It distinguishes from siblings like 'nice' and 'timeout'.

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?

Explicitly states when to use (diagnose buffering-related delays) and when not (CPU priority, time-bounded execution). Names alternatives 'nice' and 'timeout'.

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