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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds non-obvious domain behavior: a non-live environment yields containers with no working networking, which is a real diagnostic constraint an agent would not get from the structured fields alone. It does not describe result volume or paging, but for a simple list call that is minor.

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 core action and scope; the second sentence is longer but delivers the one non-obvious fact about environment state. No filler or restatement of the title.

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 compensates by stating what is returned (each environment's current state). For a two-parameter, zero-required, read-only list tool with full annotation coverage, this is essentially complete; only the exact fields per environment are unspecified.

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 100% and both parameters (context, conversation_id) carry their own explanations, including the first-call/omit-then-echo convention for conversation_id. The description adds nothing about parameters, which is the expected baseline when the schema already does the work.

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?

States a specific verb and resource ("List all environments in the authenticated Cycle hub") plus the data returned ("with their current state"). The scope (authenticated hub) helps separate it from mutating siblings like create_environment, delete_environment, or cycle_control_environment, though it never names an alternative explicitly.

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?

Usage is implied: an agent reading "list all environments ... with their current state" can infer this is the discovery/inspection call preceding environment mutations. However, there is no explicit when-to-use or when-not-to-use guidance, nor any pointer to alternatives such as get_hub or cycle_control_environment.

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