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

Annotations already flag this as destructive and idempotent, but the description adds traits the annotations cannot express: values are write-only (not readable back), changes are staged rather than live, and DENKOPS_* keys are rejected. These details directly shape how an agent should warn about, sequence, and verify the call.

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?

Four short sentences, each carrying distinct information: the action, the secret use case, the write-only semantics, the staging behavior, and the reserved-key rejection. Nothing is redundant and the action leads the text.

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 three-parameter mutation with no output schema, the definition covers what matters most: mutability, write-only values, deferred activation, and a hard rejection rule. Only minor gaps remain, such as value format or size constraints and whether an existing key's prior value is replaced silently vs. erroring.

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 only 33%, so the description should carry more weight for the undocumented key and value parameters. It does add a real constraint on key (reserved DENKOPS_* names are rejected) and characterizes value as write-only secret material, but it never states key naming conventions or value size/format limits.

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-plus-resource ('Set or overwrite a DenkOps project's environment variable') and adds the scope cue '(for secrets such as API keys)', which instantly separates it from siblings like list_env and unset_env. An agent can identify the operation without opening the schema.

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?

It gives a clear use case (storing secrets such as API keys) and an operational expectation (the change takes effect on the next deploy or redeploy), which tells the agent when the effect will land. It stops short of naming alternatives such as unset_env for removal or redeploy for applying the staged value, so the routing guidance is contextual rather than explicit.

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