env_env_list

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

With no annotations, the description carries full burden. It discloses that sensitive variables are excluded from output and that the result is a JSON object. For a simple read-only operation, this is sufficient, though it omits mention of potential cost or latency.

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 two sentences, front-loaded with the core purpose, and includes an illustrative example. No extraneous information.

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 key aspects: listing, filtering, and sensitive variable exclusion. It does not detail the output JSON structure, but the presence of an output schema (though not shown) reduces the need. Sibling context helps distinguish usage.

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 input schema has 0% description coverage for the prefix parameter. The description adds meaning by explaining it filters results (e.g., 'AWS_'), which goes beyond the schema's type and default.

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?

Description explicitly states the tool lists environment variables as a JSON object with optional prefix filtering, which clearly distinguishes it from siblings like env_env_get (gets a single variable) or env_env_check (checks existence). The inclusion of sensitive variable exclusion adds further specificity.

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 mentions passing a prefix to filter, giving an example. While it does not explicitly contrast with sibling tools, the context of listing vs. retrieving single variables is clear. Could be improved with explicit when-to-use guidance.

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