run_pipeline

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

No annotations are provided, so the description carries the full transparency burden. It discloses per-step validation, allowlist/policy checks, 200KB stdout/stderr limits, the truncation flag, and the no-shell guarantee—substantial behavioral detail.

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 front-loaded with the core purpose, then uses compact paragraphs for validation and truncation details. Every sentence contributes useful behavioral or usage information, with no filler or 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 tool's complexity and the absence of annotations, the description is strongly complete: it covers execution model, safety, and truncation behavior. The main remaining gap is failure semantics (e.g., what happens if a step exits non-zero), though the output schema may cover that.

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?

The input schema already describes all three parameters with 100% coverage, so the baseline is 3. The description adds extra meaning by explaining how steps connect via stdin/stdout and how truncation is signaled, going beyond the raw schema without re-listing parameter syntax.

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 first sentence states a specific action and resource: 'Execute a pipeline of tools, piping stdout from each step into stdin of the next.' This clearly distinguishes it from sibling tools like run_tool and run_script by emphasizing multi-step composition and pipe semantics.

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 identifies the intended use case: replacing shell piping like `strings binary | grep flag` with a safe, no-shell alternative. It does not explicitly name sibling alternatives or state when not to use it, but the context is clear.

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