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

With no annotations, the description carries full burden and does disclose key traits: it both creates and immediately starts the pipeline (a state-changing side effect), and it returns pipeline id plus initial job ids. It omits permissions, error/rollback behavior, and rate limits, so not fully complete.

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-loads the core action, then the constraints, then a useful example — no filler. The example consumes space but earns it by disambiguating the nested payload.

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 mutation tool with no annotations and no output schema, the description covers the essentials: side effect, return values (id + job ids), structural constraint, and payload format. It stops short of edge-case/error and permission details.

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 loosely typed (items: object), so the description must compensate. It does: it specifies the node {id, type, config} shape, the edge {id, from, to} shape, warns that keys are from/to not source/target, and supplies a full worked example.

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') and scopes it as multi-step, distinguishing it from single-job siblings like create_scrap_job and create_enrichment_job. The inline example makes the intended output concrete.

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?

Gives a clear prerequisite ('Call get_pipeline_schema first for the valid block types') and a structural rule ('Keep chains LINEAR'), which tells the agent how to use it. It does not explicitly say when to prefer this over create_scrap_job/create_enrichment_job, leaving that to inference.

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