pipe_runner

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

With no annotations, description carries full burden but only provides a vague action. Contradicts schema about optionality, and no disclosure of side effects, permissions, or outcomes.

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 very short (10 words), but conciseness is undermined by inaccuracy and lack of necessary information. Front-loads purpose but not effectively.

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?

Despite an output schema existing, the description fails to provide essential context for a 3-param tool with required inputs. No behavioral or usage context, and schema contradiction makes it unreliable.

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 description coverage is 0%, and description fails to explain the three required parameters (plx_content, specific_pipe_code_if_plx_content_has_no_main_pipe, inputs_json). The one mention of PLX content contradicts the schema.

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 states 'Run a Pipelex pipeline (optionally with PLX content)', but the input schema lists plx_content as required, creating a contradiction. This misleads about whether PLX content is mandatory.

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 guidance on when to use this tool versus siblings like pipe_builder or list_available_pipes. No context about prerequisites or scenarios.

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