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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered; the description adds genuine value beyond them by disclosing the destructive blast radius (project plus its deployments), permanence, and the approval precondition. It stops short of describing recovery options or error 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 tight sentences with the destructive scope front-loaded and the approval requirement immediately after. Nothing redundant or padded.

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?

Annotations carry the safety profile and the description covers blast radius and the approval gate, but for a 9-parameter destructive tool with no output schema and 0% parameter coverage, an agent still lacks guidance on the required identifiers and the BEON approval/context envelope.

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 the full burden — yet it names no parameters at all and only obliquely gestures at the approval flow that approval_id encodes. The beon_* infrastructure parameters and team_id remain completely 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+resource and scope: permanently deleting a project, and explicitly notes it also removes its deployments. This distinguishes it cleanly from siblings like vercel_delete_deployment or vercel_delete_project_routes, which operate on other resources.

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?

It supplies one prerequisite ("Requires exact user approval in BEON PASS"), which is real usage context, but gives no when/when-not guidance relative to alternatives such as deleting individual deployments or routes, and no indication of what triggers the approval flow.

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