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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description goes well beyond that by warning that production deployments change live routing, that Vercel performs installation/builds, and that credential files/literal secrets must never be included. These are exactly the operational warnings an agent needs before invoking a mutation.

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?

Five front-loaded sentences, purpose first, then behavior, target semantics, prerequisites, and the safety warning. Every sentence carries information an agent can act on; nothing is redundant with the annotations or schema.

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 12-parameter mutation with no output schema, the description covers the required parameters, source variants, target semantics, and safety, which is enough to call it correctly. It leaves the auxiliary identifiers (team_id, approval_id, beon_* context) unexplained, which is a minor gap for a tool of this complexity.

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%, so the description must carry parameter meaning. It does explain the source alternatives (files vs GitHub commit) with the 110 KB limit, the preview/production target, and the existing-project prerequisite, but it says nothing about team_id, approval_id, or the beon_* parameters, leaving roughly half the surface undocumented.

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?

States a specific verb and resource ('Create ... deployment') plus scope (FIRST or subsequent, from source files or an exact GitHub commit), which lets an agent picture the operation. It does not explicitly name or differentiate from siblings like vercel_redeploy, and 'or a subsequent deployment' slightly overlaps with redeploy, so it stops short of the sibling-distinguishing 5.

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?

Gives concrete context: source can be files or a GitHub commit, files are capped at 110 KB (use Git for larger apps), preview is the default and production can change live routing, and an existing project is required. It never names an alternative tool or an explicit 'do not use this when' clause, so it is clear guidance but not full routing guidance.

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