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

With no annotations, the description carries the full burden, and it adds real context: the call creates a persisted pipeline, the first step reads upstream data from {{workflow_input}}, and it costs one builder_call credit. It stops short of stating permission requirements or what happens on failure or credit exhaustion.

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 key facts (creates, cost, return value) are dense and front-loaded in a short paragraph with no filler. The {{workflow_input}} placeholder is slightly cryptic but is load-bearing information about behavior.

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 mutating four-parameter tool with no annotations and no output schema, the description covers cost, return, and two parameters but omits the other two parameters, required-field expectations, and any routing guidance against sibling creation tools.

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%, so the description must compensate. It well explains description (proposal new_pipelines format) and variables (keys of the workflow node's config.variables), but leaves name and workflow_name (default empty string) completely undefined, leaving half the parameters undocumented.

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?

Description states a specific verb and resource: draft a pipeline with the AI pipeline builder from a description and create it. It distinguishes itself from plain creation by naming the AI builder and the description-based drafting mode, though it never names the sibling pipeline_create it differs from.

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?

Usage is implied through 'from a description (as in a proposal's new_pipelines)', which tells the agent the input shape comes from a proposal, but there is no explicit when-to-use versus pipeline_create or the chat-based builder tools, and no exclusions stated.

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