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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false. The description adds real value beyond that: chains are linear, each block feeds the next, edge keys must be 'from'/'to' rather than source/target, and the call returns a pipeline id plus initial job ids. It doesn't discuss failure/partial-creation semantics, so not a 5.

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?

Front-loaded with the core action, then constraints, then the example. The example block is large but earns its place given the nested, free-form definition object. Minor density but no padding.

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 nested, open-world create operation with no output schema, the definition covers the shape of input, the key naming gotcha, the return values, and where to find the authoritative schema. An agent has everything needed to attempt a valid call.

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 only 50% and the nested definition object is largely unspecified, so the description compensates with a concrete worked example showing node id/type/config and edge structure. It also reinforces the from/to key convention already hinted at in the schema. It stops short of enumerating the optional 'name' parameter's role.

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 — 'Create AND start a multi-step pipeline' — with an inline example of the chaining concept, and it is clearly distinguishable from siblings like create_scrap_job or create_enrichment_job because it targets multi-step chains rather than a single job.

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?

It routes the agent to get_pipeline_schema for valid block types and config fields, which is explicit sibling delegation. It never states when NOT to use it versus a single-job creator such as create_scrap_job, so context is clear but exclusions are absent.

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