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

With no annotations, the description carries the full burden. It does not disclose whether running a step performs real side effects (e.g. sending emails, writing storage), what authentication or pipeline state is required, or whether the run is recorded in history. Only the template interpolation note is offered, which is not a behavioral trait.

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, front-loaded with the core action and no filler. It is efficient, though the terseness edges into under-specification rather than genuine conciseness.

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 tool with a required nested object parameter, no annotations, no output schema, and 0% schema coverage, the description is far too thin. An agent cannot know the shape of `step`, what this returns, or what a successful isolated run implies.

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 3 parameters, so the description must compensate and largely fails. It explains only that `previous_outputs[i]` maps to `{{step_{i+1}_output}}`, a cryptic note that leaves the required nested `step` object and `pipeline_variables` entirely 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?

The verb+resource ("Run a single step in isolation") is stated and "in isolation" hints at differentiation from pipeline_run, but the description never says what a "step" is, what pipeline it belongs to, or what testing a step entails. An agent can guess the general idea but cannot confidently distinguish this from pipeline_run or pipeline_debug_chat without opening the 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?

No explicit when-to-use guidance and no named alternatives among the many pipeline_* siblings. "In isolation" implies debugging/iteration but the description never says to prefer this over pipeline_run for validation, nor when not to use it (e.g. it does not state whether side effects occur).

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