environment_list

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

No annotations provided, so description carries the burden. It discloses read-only listing behavior, output shape (summaries), and pagination mechanism. Does not detail authentication or rate limits, but covers essential operational 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?

Three well-structured sentences. First sentence states purpose with output fields. Second and third provide crucial usage guidance and warnings. No fluff, directly actionable.

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 output schema exists, description sufficiently covers return fields and selection guidance. Lacks detail on pagination token format and any ordering, but remains adequate for a list tool with sibling 'environment_get' for deeper detail.

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 has 0% description coverage. The description partially compensates by mentioning 'Page via next_page' for pagination, but does not explain the 'limit' parameter or the format of 'page'. Adds marginal value beyond schema.

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 tool lists sandbox environments and specifies the summary fields (id, name, description, metadata). It distinguishes from sibling 'environment_get' by focusing on listing multiple environments and warns about selection importance.

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?

Explicitly advises when to use the tool: for selecting an environment to start a session. It warns against picking the first result and instructs matching via name/description/metadata. Also mentions pagination with 'next_page', giving clear context on usage.

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