Vercel MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what authentication might be required, whether rate limits apply, what happens if the file doesn't exist, or what format the contents are returned in. The description provides zero behavioral context beyond the basic action implied by the name.

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?

While technically concise with just three words, this description is under-specified rather than efficiently structured. It fails to front-load important information and doesn't use its limited space effectively. A truly concise description would pack more operational context into the same or fewer words, whereas this feels incomplete rather than efficiently crafted.

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 tool with 4 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't help the agent understand what kind of file contents are returned (text, binary, structured data), what errors might occur, or how this tool fits into the broader deployment workflow with its sibling tools. The description provides minimal context for what appears to be a non-trivial file retrieval operation.

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?

With 100% schema description coverage, the schema already documents all 4 parameters adequately. The description adds no parameter-specific information beyond what's in the schema - it doesn't explain relationships between parameters, provide examples of valid values, or clarify why certain parameters are required while others are optional. The baseline score of 3 reflects adequate schema coverage with no additional value from the description.

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 'Gets deployment file contents' is a tautology that essentially restates the tool name 'getDeploymentFileContents' without adding meaningful specificity. While it correctly identifies the verb ('Gets') and resource ('deployment file contents'), it doesn't distinguish this tool from potential siblings like 'listDeploymentFiles' or provide any additional context about what type of file contents are retrieved or their format.

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 absolutely no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or differentiate from sibling tools like 'getDeployment' or 'listDeploymentFiles'. The agent receives no help in determining when this specific file retrieval tool should be selected over other deployment-related operations.

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