pipeline

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

No annotations, so description should disclose behavioral traits. It explains that input_url replaces $INPUT_URL, but does not mention if execution is destructive, auth needs, or persistence. Moderately transparent.

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?

Well-structured with clear sections for actions and args. Every sentence adds value, no fluff.

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?

Covers parameters and actions well, but missing explanation of output or return values despite presence of output schema. Could mention that pipeline execution returns a result.

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%, but description fully explains each parameter: action values, notebook_id required for run, pipeline_name required for run, input_url as URL variable. Adds essential meaning beyond 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?

Clearly states the tool manages and executes multi-step notebook pipelines, distinct from sibling tools like notebook_query that query notebooks directly.

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?

Explicitly lists actions (run, list) and when each is applicable, with required parameters per action. However, lacks comparison to alternative tools for pipeline management.

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