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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description goes beyond them by disclosing the real-world consequence — traffic using the alias is interrupted — which is exactly the kind of impact context annotations cannot express.

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 the action and its impact in one clause. Nothing wasted, nothing buried.

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 9-parameter mutation tool with no output schema and no parameter descriptions, the description leaves most of the surface undocumented — it never explains the beon_* parameters or approval_id, and offers no auth or irreversibility guidance beyond the terse traffic warning.

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 9 parameters, with only alias_id required and no descriptions anywhere. The description implies an alias identifier is needed but explains nothing about team_id, approval_id, or the beon_* context parameters, so it 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 ('Delete an alias') and adds the operational consequence ('interrupt traffic using it'). This distinguishes it from vercel_set_alias and vercel_list_aliases, though it never names them explicitly.

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 delete an alias versus reassigning it (vercel_set_alias) or when deletion is warranted. There are no prerequisites, warnings, or alternative-tool pointers anywhere in the description.

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