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 genuine context beyond that: the downstream consequence ('future deployments may break') and the out-of-band approval requirement, which the annotations do not convey.

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 clauses, front-loaded with the action and immediately followed by the risk and prerequisite. No filler, though it is arguably too terse given the parameter surface it needs to cover.

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 10-parameter tool with no output schema, the description covers the risk and approval gate well and annotations cover the safety hints. But the many required and BEON-specific parameters are left entirely undocumented, so an agent lacks guidance on how to actually populate the call.

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, so the description must carry the meaning. It only implicitly hints at the approval mechanism (approval_id) via 'exact user approval in BEON PASS' and says nothing about project_id, variable_id, team_id, or the beon_* context fields.

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+resource ('Delete a variable'), and the tool name supplies the 'environment variable' scope, making it clearly distinct from vercel_set_environment_variable and vercel_list_environment_variables. It stops short of explicitly naming those siblings, so it isn't a full 5.

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?

Provides a real prerequisite ('Requires exact user approval in BEON PASS') and a risk warning, which give context for when the tool is appropriate. However, it names no alternative (e.g., set_environment_variable for updates) and gives no when-not-to-use guidance.

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