list_environments

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

Without annotations, the description must carry behavioral context. It explicitly states that secret material is not returned, which is a key safety behavior. However, it does not mention authentication requirements, side effects, or whether the list is filtered or paginated.

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 a single, front-loaded sentence that communicates purpose and a key behavioral trait. It is not verbose, but could be improved by adding a brief explanation of the optional parameter.

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?

While an output schema exists, the description does not explain the 'refresh' parameter or provide enough context for the agent to decide when to use this tool. The purpose is clear, but for a tool with one parameter and many siblings, it falls short.

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 single parameter 'refresh' is not explained in the description, and the schema has 0% description coverage. The description does not add any meaning beyond the schema, leaving the agent to infer its purpose.

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 clearly states the verb 'list' and resource 'environments', and adds a useful constraint about not returning secret material. It distinguishes from sibling tools like list_connections and list_integrations by its focus on environments, though it could explicitly mention this separation.

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 vs alternatives. Given the many sibling tools, explicit context about when to list environments versus connections or integrations would be helpful.

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