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

With no annotations, the description does real work: it discloses that execution is asynchronous, that a run_id comes back, and that the call consumes pipeline_run credits — the latter being a cost trait an agent must know before invoking. It does not cover failure behavior, whether the run can be cancelled mid-flight, or permission prerequisites, which leaves some burden unaddressed.

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?

Two short sentences, zero filler, action and return value front-loaded before the follow-up routing. Nothing repeats the schema or restates the name.

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?

The invocation lifecycle (start → wait/get) and cost are adequately covered, which is the core need for a fire-and-forget execution tool. But with no annotations, no output schema, and 0% parameter coverage, the definition should still explain what the three optional inputs do; an agent cannot compose a correct non-trivial call from this description alone.

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 description coverage is 0% across four parameters, so the description must carry the meaning — yet it never mentions pipeline_id, variables, skip_steps, or initial_step_outputs. The format of variables or what a 'skip step' reference looks like is left entirely to guesswork.

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?

States a specific verb and resource ('Start a run') plus the async contract and the return value (run_id). It also names the two sibling tools that continue the workflow, so it is distinguishable from pipeline_run_get, pipeline_run_wait, and pipeline_run_cancel without opening any schema.

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 says to follow this call with pipeline_run_wait or pipeline_run_get, which gives the agent a clear ordering rule and names the alternatives. It stops short of saying when NOT to use it (e.g. testing a single step via pipeline_test_step, or scheduling recurring execution via schedule_create).

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