List Experiments

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

With no annotations provided, the description carries the behavioral burden. 'List' clearly indicates a non-mutating read, and 'most recent first' plus the sandbox-lifecycle hint add useful context. It does not explicitly mention side effects or permissions, but for a simple read-only list the risk of ambiguity is low.

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 two compact sentences with no filler. The core behavior is front-loaded in the first sentence, and the second sentence adds practical usage context without redundancy.

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 both parameters are fully documented in the schema and an output schema exists, the description provides the missing decision context: when to use this tool and what ordering to expect. Nothing critical is missing for a list-only operation.

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 input schema already documents both parameters fully, including defaults, ranges, and meaning, so the description does not need to repeat them. The description adds no parameter-specific detail, but the baseline 3 applies because schema coverage is 100%.

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 action ('List'), the resource ('experiments'), and the ordering ('most recent first'). The plural resource and the sandbox-finding use case distinguish it from singular or CRUD siblings like get_experiment and create_experiment, though it does not explicitly name a competing tool.

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?

It explicitly tells the agent when to use this tool: to find a sandbox created earlier or to check for undestroyed sandboxes before creating another. It lacks an explicit 'when not to use' or alternative-name mention, which keeps it from a 5.

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