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 mutation profile is covered. The description adds genuine value with 'Can change production traffic', disclosing blast radius that the annotations don't convey, but says nothing about what happens to the previously bound alias, whether auth/approval is needed, or reversibility.

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, front-loaded sentences with no filler. The core action comes first and the risk note second, which is exactly the right ordering for a destructive tool.

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, non-idempotent mutation with 10 undocumented parameters and no output schema, the description is too thin. It omits prerequisites, the effect on any existing alias, and the meaning of the required approval/team context parameters.

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. The description implicitly maps 'hostname' to alias and 'deployment' to deployment_id, but eight parameters (team_id, approval_id, and the beon_* context fields, including a beon_environment enum) get no explanation in either the schema or the description.

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: 'Assign a hostname to a deployment', which an agent can immediately map to alias + deployment_id. It does not differentiate from near-neighbors like vercel_add_project_domain, vercel_delete_alias, or vercel_promote_deployment, so the agent must infer the boundary.

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 second sentence ('Can change production traffic') is an impact warning, not usage guidance. There is no statement of when to use this versus vercel_add_project_domain or vercel_promote_deployment, no prerequisites, and no when-not-to-use condition.

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