export_pipeline

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

No annotations are provided. The description implies the pipeline must be validated but does not disclose side effects, authentication needs, or behavior on invalid input. For a tool with zero annotation coverage, more details are needed.

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 is concise and front-loaded. It could be slightly more informative without becoming verbose.

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 availability of an output schema, the description doesn't need to detail returns. However, it lacks usage context and setup prerequisites, making it minimally adequate for a 2-parameter tool.

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 0%; the description does not add meaning to the parameters beyond listing the enum values for output_format. It omits explanation of the pipeline object structure or constraints.

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 action (export), resource (validated pipeline), and output formats (Python, JSON, YAML). It effectively distinguishes the tool from siblings like adjust_pipeline or explain_pipeline.

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 mentions 'validated pipeline' implying a prerequisite, but it does not provide explicit guidance on when to use vs alternatives, nor does it state conditions or exclusions.

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