list_sandboxes

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

With no annotations present, the description carries the disclosure burden. It reveals ordering behavior ('newest first') and account scoping, and the verb 'list' implies a non-mutating operation. However, it does not explicitly state that deleted sandboxes are excluded unless include_deleted is set, though the schema covers that.

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?

Two short sentences, front-loaded with the core purpose and ordering. The second sentence adds practical guidance without redundancy or fluff.

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 simple two-parameter list tool with no output schema, the description is mostly sufficient: it gives purpose, ordering, and a use case. The only minor gap is not clarifying that destroyed sandboxes are excluded by default, which could affect the 'find sandboxes you created earlier' use case; however, the schema's include_deleted description partially compensates.

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 description coverage is 100%, so both parameters are already fully documented. The tool description does not add any extra meaning to the parameters, so the baseline of 3 applies.

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 the exact operation ('List the sandboxes on this account') and specifies ordering ('newest first'), making the tool's purpose immediately clear. This clearly distinguishes it from siblings like create_sandbox, destroy_sandbox, or get_sandbox, which either mutate or target a single sandbox.

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 provides a concrete use case ('Use it to find sandboxes you created earlier'), indicating this tool is for discovery and recall. It does not explicitly name alternatives or exclusions, so an agent might not know when to prefer get_sandbox instead, but the context is clear enough for most list scenarios.

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