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

Annotations already flag this as a non-read-only, destructive, closed-world mutation. The description adds the concrete transition model, which is useful context, but does not disclose what gets overwritten in the target environment, whether the promotion is reversible, or what the returned state looks like despite an output schema existing.

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 front-loaded sentence with zero filler; the parenthetical transition list is the only content and it directly serves parameter semantics.

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?

Given a destructive mutation with an output schema, the description covers the what and the allowed transitions but omits operational context an agent needs: effect on the target environment, reversibility, and any confirmation requirements. Adequate but with clear gaps.

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 100% and the anyOf enforces the exact dev->test / test->prod pairs, so the schema fully documents parameters. The description only restates those transitions in prose without adding format or validation detail beyond the schema.

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 (Promote) and resource (a deployment version), and enumerates the exact environment transitions (Dev to Test, Test to Prod). This clearly distinguishes it from deployment_deploy, deployment_rollback, and deployment_undeploy.

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 implies the usage context by naming the specific env transitions, but does not explicitly state when to use this versus deployment_deploy or deployment_rollback, nor any prerequisites such as the source environment needing an existing deployment.

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