pipeline_create

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

Annotations already declare this as a non-read-only, non-destructive mutation, and the description adds essentially no behavioral context beyond restating the create action. It does not mention permissions, whether the pipeline is created empty, whether any definition is required, or what side effects might occur.

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?

A single sentence with zero redundant or filler words. The verb and object are front-loaded, making the core purpose immediately scannable. Nothing in the description wastes the agent's attention.

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 tool is simple with only 3 documented parameters and no nested objects, and annotations cover the safety profile. However, there is no output schema and the description does not mention what is returned on success, whether a definition is needed, or workspace prerequisites, so some operational context is missing.

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 100%, so all three parameters already have descriptive text. The tool description adds no parameter-level meaning beyond the schema, which aligns with the baseline score of 3 when the schema handles parameter documentation.

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 states a specific verb ('Create'), a clear resource ('a new data pipeline'), and a scope ('in a workspace'). This unambiguously distinguishes it from related sibling tools like pipeline_update, pipeline_delete, and pipeline_list, and leaves no doubt about the operation being performed.

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?

The description gives no explicit guidance on when to use this tool instead of alternatives, nor any prerequisites such as requiring an existing workspace ID. No mention is made of related operations like pipeline_create_schedule, so usage context must be inferred entirely from the tool name and sibling tool list.

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