create_pipeline

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

Discloses that agents run in sequence and each receives previous output. However, with no annotations, missing details on idempotency, uniqueness constraints, or error behavior (e.g., duplicate name).

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?

Single sentence, front-loaded with purpose. No extraneous information. Efficient and clear.

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 no annotations and no output schema, description omits return value (likely pipeline ID) and error scenarios. Adequate for creation but not fully complete 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 descriptions cover all 4 parameters (100% coverage). The tool description adds minimal extra: only the sequential chaining behavior. Baseline 3 is appropriate as schema already provides meaning.

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 'Create a new pipeline' with specific verb and resource. It distinguishes from siblings like run_pipeline (execution) and list_pipelines (listing) by focusing on creation.

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?

Implies usage for creating a pipeline, but lacks explicit when-to-use vs alternatives like run_pipeline. No prerequisite guidance (e.g., agents must exist, listing via list_agents is hinted in schema but not description).

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