List Environments

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

No annotations are provided, so the description carries the burden. It discloses that the tool lists configured environments and gives examples, but it does not disclose whether this is a read-only operation, whether it hits AWS APIs or a local config, or whether it can fail. The behavior is simple enough that a 3 is fair, but more context would help.

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?

One short sentence that is front-loaded with the verb and resource, and includes useful examples. No wasted words.

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 zero-parameter list tool, the description is mostly complete. However, there is no output schema detail in the description and no mention of whether the list is from local config or AWS, which could matter for an agent deciding between this and get_environment_info. The output schema exists, so return values are covered, but the source of truth is ambiguous.

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 has zero parameters, so the schema provides no semantics to add. The description adds the meaning of the output scope ('all configured AWS environments') and examples. With 0 params, baseline 4 is appropriate.

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 states a specific verb ('List') and resource ('all configured AWS environments'), and gives examples of what those environments are (production, localstack). It is clear and distinguishes from siblings like list_profiles and list_accounts, though it doesn't explicitly name a sibling.

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 implies usage: call this to see configured environments. It does not explicitly state when to use this vs. switch_environment, get_environment_info, or compare_environments, which are sibling tools that also relate to environments. No exclusions or alternatives are given.

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