create-pipeline

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The one-line description 'Create a new pipeline' gives no information about mutation behavior, idempotency, error conditions, or side effects, which is severely lacking for a create 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?

The description is extremely concise at one sentence, which is front-loaded. However, it is too terse and lacks necessary detail; it is not well-structured for understanding the tool's purpose beyond the name. It earns its place but could be slightly expanded.

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 has 8 parameters (2 required) and no output schema. The one-line description does not explain the return value, the effect of creation, or how it relates to other pipeline entities. For a complex entity with many parameters, the description is insufficiently complete.

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% with all parameters having descriptions, so the baseline is 3. The tool description does not add any additional meaning or context beyond what the schema already provides, hence it meets but does not exceed the baseline.

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 clearly states the action 'Create' and the resource 'pipeline', which is a specific verb+resource. However, there are many sibling 'create-*' tools (e.g., create-chart, create-database) and the description does not distinguish what a pipeline is in this context, so it lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. Given the large number of sibling 'create-*' tools, there is no context about prerequisites, scenarios, or trade-offs.

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