Vercel MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Lists') without details on permissions, rate limits, pagination, or output format (e.g., list of file names vs. full metadata). This is inadequate for a tool with potential complexity, as it lacks critical operational context.

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 a single sentence, 'Lists deployment files', which is front-loaded and wastes no words. It efficiently conveys the core action without unnecessary elaboration, making it easy 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 no annotations, no output schema, and a tool that likely returns a list of files (implied by 'Lists'), the description is incomplete. It does not address what the output includes (e.g., file names, sizes, types) or behavioral aspects like error handling. For a tool with three parameters and potential complexity, this leaves significant gaps in understanding.

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 schema (deploymentId, slug, teamId). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., slug vs. teamId) or usage examples. This meets the baseline for high schema coverage but does not enhance understanding.

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 'Lists deployment files' states the basic action (list) and resource (deployment files), which provides a minimal viable purpose. However, it lacks specificity about what 'deployment files' entails (e.g., file metadata, paths, types) and does not distinguish it from sibling tools like 'getDeploymentFileContents' or 'getDeployment', making it vague but functional.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a deployment ID), exclusions, or comparisons to siblings such as 'getDeploymentFileContents' (which likely retrieves file content) or 'getDeployment' (which might provide deployment metadata). This leaves usage unclear.

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