env_env_get

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

Without annotations, the description carries full burden. It discloses sensitive variable hiding, which is excellent. However, it fails to clarify the interaction between the `default` parameter and the 'null' return when the variable is unset, leaving ambiguity about exact behavior.

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 concise, using three short sentences without redundancy. Each sentence adds value: purpose, return type, and special behavior. It could be slightly more structured but is efficient.

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?

Given the tool's simplicity, the description covers purpose, return, and hidden behaviors. However, it misses key details about the default parameter and error handling (e.g., what happens if the key is invalid). With no output schema details provided, agents may lack full clarity.

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?

The schema has 0% description coverage, so the description must explain parameters. It implicitly covers `key` but omits any explanation of the `default` parameter, which is defined in the schema. This leaves agents unaware of how to use the default fallback.

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 it gets the value of a single environment variable, using a specific verb-resource pair. It distinguishes from siblings like `env_env_list` by focusing on a single variable and also mentions sensitive variable behavior, which is unique to this tool.

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 implies usage when you need a single variable value but does not explicitly contrast with alternatives like `env_env_list` or `env_env_set`. No when-not-to-use guidance is given, though the hidden behavior hint is useful.

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