zadig_environment_list

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'List', which implies read-only behavior, but it does not disclose what environments are returned, whether production/non-production are included, or how filtering behaves.

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 short and free of filler, but it is under-specified. It is concise rather than overly verbose, yet it omits enough useful context that it reads more as a stub than a considered tool definition.

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 list tool with two optional parameters and no annotations, the single-sentence description is not complete enough. It lacks parameter semantics and usage guidance; the presence of an output schema reduces the need to describe return values, but the missing contextual details still leave a significant gap.

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 zero description coverage, and the tool description adds no explanation of the 'production' or 'project_key' parameters. It does not clarify that production likely filters for production environments or that project_key scopes the listing to a specific project.

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 a specific verb ('List') and resource ('Zadig environments'), clearly indicating a read-only enumeration operation. It is distinguishable from sibling tools like environment_get, which implies retrieving a single environment, though it does not explicitly make that contrast.

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 no guidance on when to use this tool versus alternatives such as environment_get or environment_service_list. There is no mention of filtering by project or production status, and no exclusions or conditions are stated.

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