Manage application env vars

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

The description discloses key behavioral traits: list masks secrets unless showSecrets is set, upsert is idempotent (create or update by key), and delete requires env_uuid. These go beyond the annotations (readOnlyHint false, destructiveHint false) by offering operational details. However, it doesn't describe the full behavior of create/update or response format.

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?

The description is a single, information-dense sentence that leads with the core purpose and then enumerates actions. No redundant or filler words.

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 10 parameters, 6 actions, and no output schema, the description covers actions but omits parameter requirements per action (e.g., that create/update likely need key and value). It also doesn't describe return values. More detail is needed for an agent to invoke this correctly.

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 30%, and the description only clarifies a few parameters: showSecrets, envs, and env_uuid. It fails to explain key, value, is_literal, is_preview, is_multiline, which are undocumented in the schema. For a 10-parameter tool, this is insufficient compensation.

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 clearly states the tool manages environment variables for an application, using the verb 'Manage' and resource 'application env vars'. It distinguishes from sibling tools like databaseEnvs and serviceEnvs by specifying 'application'.

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 provides context that this is for application environment variables, differentiating it from databaseEnvs/serviceEnvs. It also gives action-specific usage notes like 'list (secrets masked unless showSecrets)' and 'delete (needs env_uuid)', but does not explicitly say when not to use this tool.

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