list_environments

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

With no annotations, the description carries the full burden. It simply says 'List all environments' without disclosing that a workspaceId is required, whether it is a read-only operation, or any details about the response format. This is insufficient for a tool with no other behavioral info.

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 extremely short at five words, which is efficient but under-specified. It lacks essential context about workspace scoping and the nature of the result, making it more under-specification than good conciseness.

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?

Given that there is no output schema and no annotations, the description should explain the scope and return behavior. It does not specify that the list is filtered by workspaceId, nor what fields are returned. The presence of sibling tools like get_environment suggests a need to clarify the list vs. single-item distinction.

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 schema provides a full description for the only parameter (workspaceId), covering 100% of parameters. The tool description adds no additional meaning, such as how workspaceId filters the list. Baseline of 3 is appropriate since schema covers the parameter but the description doesn't enhance it.

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 uses a specific verb 'list' and resource 'environments', clearly identifying the action. However, it does not mention that environments are scoped to a workspace (evidenced by the required workspaceId), which distinguishes it from a global listing. Sibling tools like get_environment and list_workspaces are not referenced, but the basic purpose is clear.

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 usage guidance is provided. The description does not specify when to use this tool versus get_environment (for a single environment) or list_workspaces (for workspaces). There are no context cues for when this is the right choice.

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