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

With no annotations, the description carries the full burden, and it does disclose one critical side effect: the env is restarted so the change takes effect. That is genuinely useful behavioral context. It omits overwrite semantics for existing keys, permissions required, and whether the restart causes downtime.

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?

Two short sentences, front-loading the action and then the side effect with zero filler. Efficient, though slightly terse given the operation's risk profile.

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?

A four-required-parameter mutation with no annotations and no output schema needs more: overwrite behavior, auth requirements, and restart impact are all unstated. The restart note is a start but leaves significant gaps for a mutating tool.

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 50%: only env and project are documented in the schema, leaving key and value bare. The description adds no meaning to any of the four parameters, so it fails 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?

States a specific verb+resource: setting an environment variable, scoped to an environment. It is readily distinguishable from env.secrets.unset/import/list by the action word, though it doesn't explicitly name those siblings.

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 guidance on when to use this versus env.secrets.import (bulk) or env.secrets.unset, and no prerequisites or exclusions are given. The agent must infer the single-key vs bulk distinction from the name alone.

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