fabric_run_pipeline

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

Annotations are empty, so the description must convey behavior. It only states 'Run a data pipeline on demand' without detailing execution model (sync/async), side effects, auth requirements, or error cases. This is insufficient for a run operation.

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 sentences, front-loaded purpose with no wasted words. Highly efficient.

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?

Given the absence of output schema and annotations, the description is too sparse. It fails to explain return behavior, failure modes, or post-run state. A run tool demands richer context.

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 67% (pipelineId and workspace have descriptions). The description adds 'Optionally pass executionData (parameters)', which clarifies its role but does not elaborate on structure. executionData remains vague, and the description does not fully compensate for the missing schema doc.

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 description 'Run a data pipeline on demand' clearly states the action (run) and the resource (data pipeline). It distinguishes the tool from sibling tools like fabric_create_pipeline or fabric_run_notebook by specifying the resource type, though it does not explicitly differentiate from other 'run' tools.

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 guidance is provided on when to use this tool versus alternatives such as fabric_run_dataflow or fabric_run_notebook. The description only mentions optional executionData, lacking any context on prerequisites or selection criteria.

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