list_sandbox_containers

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful scope by clarifying that it returns containers in the sandbox's own Docker, including compose app containers, but does not describe return shape, pagination, or filtering behavior.

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 short and front-loads the resource scope. However, it is written as two fragments rather than a complete sentence, and the HTTP endpoint detail is somewhat mechanical.

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 read-only list tool with one simple parameter and no output schema, the description covers the core scope. It still omits what the returned container records contain and whether all containers or only running containers are included.

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?

There is one required 'name' parameter with 0% schema description coverage. The description compensates somewhat by showing the path /sandboxes/{name}/containers, which implies that 'name' identifies the sandbox, but it does not explicitly define the parameter.

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 identifies the resource as containers in the sandbox's own Docker and distinguishes them from compose-project apps and other containers. The HTTP GET path reinforces that this is a read/list operation, though the verb 'list' is not stated explicitly.

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 versus alternatives such as list_sandbox_images or list_sandbox_volumes. It also does not state any prerequisites or exclusions.

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