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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral content by enumerating what the catalog contains (including a custom Docker image option), but it does not describe the shape of the returned entries or note that the list may evolve. Adequate, not rich.

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, front-loaded with the content of the catalog and closed with the actionable handoff to create_instance. The long enumeration is informative rather than padding, though slightly dense.

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 output schema, the description carries the burden of explaining the return, and it does so at the level of catalog contents plus the `slug` field an agent must use. The only minor gap is not stating the exact returned entry structure, but nothing critical to invoking the call is missing.

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 tool takes zero parameters, which is the baseline-4 case. The description still surfaces the `slug` field that the sibling create_instance consumes, giving useful semantic context even though this tool itself has no inputs to document.

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 names the resource explicitly (ready environments a server can start with) and enumerates the concrete templates available, so an agent knows exactly what this call yields. The verb 'list' is only implied by the name, but the content is unambiguous and clearly distinct from siblings like list_gpu_models or list_instances.

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 second sentence gives direct, actionable routing: pass the `slug` as `template` to create_instance, which ties this read call to the downstream write call. It does not state explicit exclusions, but for a parameterless catalog call the when-to-use context is effectively covered.

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