deployment_pipeline_create

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the tool is known to mutate without being destructive. The description adds only that a new pipeline is created, which largely restates the tool name. It does not disclose what creation entails, what is returned, or any side effects beyond existence of the resource.

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 a single, compact sentence with no filler. It is appropriately short for a simple CRUD tool, though it could have included one or two extra clauses about usage context without becoming verbose.

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?

This is a simple two-parameter create operation with a fully documented schema and no output schema. The description is minimally sufficient for an agent to understand that it creates a deployment pipeline, but it omits any mention of follow-up steps, return behavior, or distinguishing context among the many deployment_pipeline_* siblings.

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 the input schema fully documents both parameters: displayName and description. The description adds no parameter-level information, but none is needed because the schema already carries the semantic weight. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'Create a new deployment pipeline.' It is clear this is a creation operation, which semantically distinguishes it from sibling operations like update, delete, get, and deploy. However, it does not explicitly name or contrast any sibling, so it stops short of a top score.

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 about when to use this tool versus alternatives such as deployment_pipeline_update, deployment_pipeline_deploy, or deployment_pipeline_get. The create verb implies usage, but there are no conditions, prerequisites, or exclusions stated.

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