create_pipeline

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

With no annotations, the description carries the full burden of behavioral disclosure. It adequately states that the tool creates a pipeline template, requires a pipeline_config conforming to a specification, and returns template details including template_id. It stops short of describing permissions, side effects, or failure modes, but the reference to the generation rules tool indicates where to find deeper behavioral context.

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 efficiently structured with a one-line purpose, per-parameter explanations, and a return clause. Every sentence adds value, and the most critical information (the need to call get_pipeline_generation_rules first) is front-loaded within the pipeline_config explanation.

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?

For a creation tool with nested objects and no output schema, the description provides sufficient context to invoke it correctly: it names the required fields in pipeline_config, points to the rules tool and docs, and reports the key return field (template_id). It could be more complete by outlining error scenarios, but it is adequate for an agent to act.

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 schema provides only type information with 0% description coverage, so the description must compensate. It fully explains each parameter: name as a human-readable template name, pipeline_config as a complete JSON workflow config with mandatory start_node_id and nodes list, and description as optional human-readable text. This goes well beyond the schema and provides actionable 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 opens with a specific verb-resource pair: 'Create a new workflow pipeline template in Colba.' This clearly distinguishes it from sibling tools like list_pipelines, update_pipeline, and archive_pipeline, making the tool's purpose unambiguous.

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 provides a concrete usage directive by instructing the agent to 'Call get_pipeline_generation_rules tool first to inspect the required format.' This establishes a prerequisite and helps the agent avoid errors. It does not explicitly mention when to use alternatives, but the resource specificity implicitly differentiates it from update/archive tools.

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