vercel_list_deployments

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

No annotations, so description must carry full burden. Only states 'list deployments', no info on authentication, pagination, rate limits, or read-only nature. Minimal behavioral disclosure.

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?

Single sentence, concise but overly sparse. Lacks necessary detail to be effective. Not poorly structured but insufficient.

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?

No annotations, no output schema, 3 params with 0% coverage. Description provides almost no context about usage, prerequisites, or results. Very incomplete.

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%, description must compensate but doesn't. No explanation of projectId, limit, or api_key. Only vague 'for a project' hint.

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?

Description clearly states verb (List), resource (deployments), and scope (for a project). Distinguishes from siblings like vercel_get_deployment (single) and vercel_list_projects (different resource).

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 on when to use this tool vs alternatives (e.g., vercel_get_deployment). No prerequisites, context, or exclusions provided.

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