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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no pagination behavior, no filtering semantics, no scope (team/project) — so it contributes almost no behavioral value.

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?

It is short, but this is under-specification rather than conciseness; a single four-word sentence cannot carry the burden of a 10-parameter list tool.

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 read-only list tool with 10 optional parameters, two enums, no output schema, and no annotation guidance on filtering, the description is wholly inadequate — an agent cannot know how to scope or paginate the query.

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?

Ten parameters with 0% schema description coverage and no explanation in the description. Limit, team_id, project_id, approval_id, and the beon_* parameters are completely undocumented in both places, which is a severe gap for a 10-param tool.

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?

"List deployment states" essentially restates the tool name vercel_list_deployments. The word "states" adds a faint hint that it returns status values, but no scope, filters, or distinction from siblings like vercel_get_deployment or railway_list_deployments is given.

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 when-to-use guidance at all. It never says when to call this versus vercel_get_deployment for a single deployment or versus the many other list_* siblings, leaving selection entirely to inference.

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