vercel_get_env

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — in particular it never explains the existence or effect of the decrypt parameter, which likely exposes plaintext secrets and is exactly the kind of behavior an agent needs warned about.

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?

A single front-loaded sentence with no filler. It is concise but under-specified rather than efficiently dense.

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?

With six parameters at 33% coverage, no output schema, and a secret-bearing decrypt flag left undocumented, the definition leaves out information an agent needs to call this correctly and safely. Nothing about return shape (names, values, targets/environments) is conveyed.

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 only 33%: project_id and the two aliases (projectId, teamId) are described, but api_key, decrypt and team_id carry no explanation anywhere. The description does not compensate — it says nothing about team scoping, alias precedence, or what toggling decrypt does to the returned values.

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 (Get), resource (environment variables) and scope (a Vercel project), which is enough for an agent to identify the operation. It does not distinguish itself from sibling env tools such as vercel_create_env, vercel_delete_env or render_list_env_vars, so it stops short of a 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?

The description gives no when-to-use/when-not-to-use guidance and never mentions the related create/delete env siblings or when reading env vars is the right call versus listing projects or deployments. Usage must be inferred 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.