Promote DevOps Center Work Item to Stage

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds no further behavioral detail (e.g., side effects, permissions, reversibility). With annotations covering the safety profile, this is acceptable but minimal, scoring 3.

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 two main sentences are concise and useful. The subsequent parameter list duplicates schema information, adding redundancy. This minor waste prevents a perfect 5, but overall it's efficient.

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 simple two-parameter mutation tool with no output schema, the description sufficiently explains purpose and usage. It lacks prerequisite or side-effect details, but given the tool's simplicity, it's adequate. Scoring 4.

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 covers both parameters with descriptions identical to those repeated in the description. Since schema coverage is 100%, the description adds no extra semantic value beyond the schema, matching the baseline of 3.

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?

Description clearly states the action: 'Promotes a DevOps Center work item to a specific pipeline stage by ID.' It specifies the resource (DevOps Center work item) and mechanism (by ID). However, it doesn't distinguish from the similarly named sibling sf_devops_promote_work_item, so it misses the full 5.

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?

States when to use: 'Use to move work items forward in the pipeline when you know the exact target stage.' This provides clear context, but there are no exclusions or explicit alternatives mentioned, landing at 4.

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