Vercel MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Deletes' implies a destructive, irreversible mutation, but the description doesn't specify permissions required, confirmation steps, side effects (e.g., whether associated resources are removed), or error handling. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is extremely concise with 'Deletes a deployment'—a single, front-loaded sentence that directly states the tool's purpose without any wasted words. It efficiently communicates the core action and resource, making it easy for an agent to parse quickly.

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?

Given the tool's destructive nature and lack of annotations or output schema, the description is incomplete. It doesn't address critical context like what deletion entails (permanent vs. reversible), prerequisites, or expected outcomes. For a mutation tool with no structured safety hints, more descriptive detail is needed to guide safe and correct usage.

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 100%, with all parameters documented in the input schema (e.g., 'deploymentId' as required). The description adds no additional meaning beyond what the schema provides, such as explaining parameter relationships or usage examples. With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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?

The description 'Deletes a deployment' clearly states the action (delete) and resource (deployment), which is a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'cancelDeployment', which might serve a similar destructive purpose but with different semantics. The purpose is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools (e.g., 'cancelDeployment', 'getDeployment'), but the description doesn't explain when deletion is appropriate versus cancellation or retrieval. No context or exclusions are mentioned, leaving the agent without usage direction.

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