Migrate from Vercel to Varity

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

Annotations already indicate destructiveHint=true. The description adds context by detailing the transformation steps (removing vercel.json, @vercel/* packages, etc.) and the output (deployment URL + report). No contradictions with annotations.

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 two sentences, front-loads the main action, and contains no redundant information. Every sentence serves a purpose.

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?

The description covers the key aspects: what it does, which projects it works with (Next.js), and the return value (URL and report). No output schema exists, but the return information is provided. Could mention prerequisites (e.g., GitHub access) but not critical.

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 coverage is 100%, so the baseline is 3. The description provides context for the parameters (e.g., 'The repository will be cloned to a temporary directory') but does not add significant meaning beyond what the schema already provides.

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 clearly states the tool's purpose: 'Migrate a Vercel project to Varity in one step'. It details the specific actions (clone, remove artifacts, deploy) and distinguishes from siblings like varity_deploy and varity_create_repo by focusing on the migration workflow.

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 explicitly says 'Use this when a developer wants to move their Vercel app to Varity' and notes it works with Next.js projects. While it doesn't list when not to use or alternative tools, the context is clear enough for an AI agent to select this over other sibling tools.

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