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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the write/destructive nature is covered. The description adds genuinely new behavior — that the deletion is permanent and gated behind an exact-approval workflow in BEON PASS — which the annotations do not convey. It stops short of describing what is destroyed (artifacts, logs, aliases) or error/denial behavior.

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 with zero filler, and the core action ('Permanently delete a deployment') is front-loaded ahead of the prerequisite. Nothing is repeated from the schema or annotations.

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, destructive, no-output-schema tool, the description is very thin: it never explains the BEON PASS approval mechanism, what an approval_id is, or how the beon_context/connection fields are populated. An agent could not reliably construct a valid call from this description plus the bare schema.

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, so the description carries full responsibility for parameter meaning and does not deliver. It implies an approval step (mapping loosely to approval_id/beon_context), but leaves the beon_* context fields, team_id, the environment enum, and the required deployment_id entirely unexplained.

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 ('delete') and resource ('a deployment'), and the qualifier 'Permanently' implies irreversibility as opposed to a soft cancel. It does not explicitly distinguish itself from the sibling vercel_cancel_deployment or vercel_rollback, leaving the boundary to inference.

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 description gives one real usage constraint — that an exact user approval in BEON PASS is required — which is actionable context. It offers no guidance on when to delete versus cancel, redeploy, or roll back a deployment, so the choice among several siblings is left implied.

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