run_pipeline

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

With no annotations, the description carries the full burden, and it does disclose real behavior: execution follows topological dependency order and node outputs are collected. It stops short of failure handling, blocking vs async behavior, and whether the pipeline definition is mutated, which matter for an executor tool.

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?

A single sentence with zero filler, and the core action ('Execute pipeline DAG') is front-loaded ahead of the qualifying details.

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 an executor with no output schema, the description should say more about what is returned (per-node outputs? aggregate?) and what happens on node failure. It conveys the ordering guarantee but leaves the return contract and error semantics implicit.

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 100%, so pipeline_id and initial_data are already documented, including that initial_data is injected into root nodes. The description adds no parameter-level detail beyond what the schema states, so the baseline 3 applies.

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?

Names a specific verb ('Execute') and resource ('pipeline DAG') and adds execution semantics ('topological dependency order', 'collect node outputs') that no sibling provides. It clearly occupies the execution slot among create/connect/add/get/export/list siblings, though it does not name them to sharpen the contrast.

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?

There is no statement of when to run this versus inspecting a pipeline first, no prerequisites, and no mention of alternatives such as list_pipelines or get_node_output. The agent must infer that this is the terminal, run-the-graph action.

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