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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral fact beyond the annotations: that live routing changes. It does not disclose auth/approval requirements or reversibility, so it is only modestly additive.

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?

Two short sentences, zero filler, and the action is front-loaded before the side effect. It is efficient, though the second sentence could carry more weight given the gaps elsewhere.

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 destructive mutation with 10 undocumented parameters, an approval pathway, and no output schema, the description is too thin. It omits required inputs, approval semantics, and what happens to prior deployments, leaving the agent under-informed at call time.

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% across 10 parameters, and the description explains none of them. Non-obvious inputs like approval_id and the beon_* context fields are left entirely undocumented, so the description fails to compensate for the coverage gap.

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 and resource (roll back production to a previous deployment) that a reader can distinguish from promote/redeploy siblings by name. However, it does not explicitly contrast itself with vercel_promote_deployment or vercel_redeploy, which are the closest alternatives.

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 on when to use this versus the sibling promote/redeploy/cancel tools, and no prerequisites or approval workflow mentioned. The only context offered is a side-effect warning ('Changes live routing'), which is not usage routing.

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