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

With no annotations, the description carries the full burden of behavioral disclosure. It states the core effect that a previous deployment becomes current, but it omits critical details such as whether the current deployment is replaced, whether traffic is switched, whether the operation is reversible, and what permissions are required.

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 definition is a single front-loaded sentence with no wasted wording. Its brevity is appropriate structurally, though the sentence is under-specified rather than richly concise.

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 deployment-mutating operation with no annotations, no output schema, and zero parameter description coverage. The one-sentence description is insufficient for an agent to call it safely and correctly without additional behavioral and parameter context.

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 0%, so the description must compensate for undocumented parameters. It only indirectly suggests that deployment_id refers to the previous deployment and site_id identifies the environment, without explaining formats, valid values, or whether deployment_id is the target or current deployment.

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 action and resource: promoting a previous deployment back to current for its environment. This is clear enough to understand the operation, but it does not differentiate from the sibling promote_staging_to_prod or clarify the distinction between 'promote' and the tool name 'rollback'.

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?

There is no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no conditions or exclusions. The phrase 'for its environment' gives scope but does not tell the agent when this rollback should be chosen over other deployment operations.

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