Update environment variables

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

The description explains the replace behavior and confirms the PUT method, adding context beyond the idempotentHint annotation. It does not contradict annotations (readOnlyHint=false, destructiveHint=false).

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 concise sentences, no redundant information. Front-loaded with the action and scope.

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 mutation tool with no output schema, the description covers the essential behavior (replace all env vars) and references the API. It could mention that the body must represent the full desired set, but the 'replace all' phrasing suffices.

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 100%, so the schema fully defines parameters. The description adds no extra semantics beyond the 'replace all' context, which is already implied. Baseline 3 is appropriate.

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 uses specific verbs ('Update', 'Replace'), names the resource ('environment variables for a service'), and includes the API endpoint, making the purpose unambiguous and distinct from siblings like get or delete.

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 states that it replaces all environment variables, but does not explicitly contrast with partial update tools (e.g., render_update_env_var) or provide when-to-use guidance. The 'replace' implication is clear but could be more explicit about alternatives.

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