list_sandbox_files

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

No annotations are provided, so the description carries the full burden. It states the exact command executed, which indicates the read-only nature and the output format. It doesn't explicitly mention side effects, but for a list operation, this is reasonably transparent. The description adds value beyond the name by specifying the directory and command.

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 a single, well-structured sentence that front-loads the action and resource, followed by the exact command. Every word earns its place, with no 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?

For a simple parameterless tool, the description is complete. It explains what the tool does and the exact return format (output of `ls -la /tmp`), which satisfies the lack of an output schema. No additional context is needed.

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?

With zero parameters and schema coverage at 100%, the baseline is 4. There is nothing to explain about parameters; the description correctly doesn't add unnecessary parameter information.

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 specifies the verb 'List' and the resource 'files in the sandbox container's /tmp directory'. It also provides the exact command output (`ls -la /tmp`), making it unambiguous and distinguishable from sibling tools like upload/download/reset.

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 clearly implies when to use this tool: whenever you need to see the files in the sandbox's /tmp directory. Although it doesn't explicitly exclude alternatives or name them, the context is clear enough given the absence of any other listing tool among siblings.

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