list_environments

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing — not whether this is read-only, whether it paginates, or what it returns. 'List' implies a read, but no behavioral trait beyond the one-word verb is conveyed.

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, but this is under-specification rather than conciseness — it is a two-word phrase that fails to earn its place by conveying any usable 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?

With no annotations, no output schema, and an undocumented required parameter, the definition is completely inadequate for correct invocation. Nothing tells the agent what to pass for type or what will come back.

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?

There is one required parameter ('type') with 0% schema description coverage, and the description says nothing about it. The agent cannot know what values 'type' accepts or what it filters — a critical gap since it is required.

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 'List environments' merely restates the tool name with no added specificity. It doesn't clarify what an 'environment' is in this context (PHP runtime? software package? node runtime?), and with siblings like install_environment and uninstall_environment nearby, the agent gets no help distinguishing the listing scope.

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?

No indication of when to use this tool versus alternatives such as install_environment, uninstall_environment, or the other list_* tools. There is no context, prerequisite, or exclusion guidance of any kind.

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