environment_get_variables

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

With no annotations provided, the description carries the full burden. It discloses that values are redacted and filtering is client-side. However, it does not mention authorization requirements, rate limits, or behavior for invalid environment IDs or empty results.

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 sentences, zero wasted words. Front-loaded with purpose and filtering capability, followed by a clear usage alternative. Ideal conciseness.

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?

The description is mostly adequate for a simple list tool, covering purpose, redaction behavior, and an alternative use case. However, it lacks explanation of the 'environmentId' and 'limit' parameters, and does not describe the output format, which would be helpful given no output schema.

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 0%. The description only explains that 'query' supports filtering by variable name. It does not clarify the 'environmentId' or 'limit' parameters, leaving the agent to infer their purpose from the schema names alone.

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 retrieves environment variables with redacted values and supports client-side filtering by name. This distinguishes it from siblings like environment_get_variable (single variable) and environment_reveal_variable (reveals values).

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 explicitly advises against using this tool when a secret is needed by a command or script, recommending op_script_run with envSecretRefs instead. However, it does not differentiate when to use this tool versus its direct siblings like environment_get_variable or environment_reveal_variable.

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