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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description still adds a genuinely important behavior not in the annotations: values are never returned, only metadata. It omits pagination and permission behavior, which keeps it short of a 5.

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?

Seven words, front-loaded with the verb and resource, and the most decision-relevant constraint ("never return values") is placed where it will be read. It is efficient, though so terse that it arguably trades completeness for brevity.

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 9-parameter tool with zero schema description coverage and no output schema, a single clause is not enough: the agent does not learn the listing scope, how environment/target filtering works, or how the beon_* parameters relate to the call. The redaction note is the only substantive content.

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?

The schema has 9 parameters at 0% description coverage, including the required project_id and the team_id/beon_* routing fields, and the description explains none of them. It provides no scoping, filtering, or identification guidance to compensate for the coverage gap.

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 states a specific verb ("List") and resource ("variable"), and the qualifier "metadata only" separates it from value-returning reads and from the sibling write tools vercel_set_environment_variable / vercel_delete_environment_variable. It is clear, though it never names the project/environment scope the listing applies to.

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?

There is no when-to-use guidance, no statement of prerequisites (the schema requires project_id), and no routing to or away from alternatives such as vercel_set_environment_variable or vercel_delete_environment_variable. The agent must infer usage entirely from the name.

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