List sandbox files

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful scope and return-entry details, but does not disclose error behavior, pagination, hidden-file handling, or symlink 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?

Two compact sentences with no wasted text. The core action and scope are front-loaded, followed by path resolution and documentation context.

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 read-only listing tool with rich annotations and no output schema, the description covers the key return fields and path semantics. It could be slightly more complete by noting whether listing is recursive or how missing paths are handled.

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 only 50%: sandboxId is documented in the schema, while path is not. The description compensates meaningfully for path by explaining that relative paths start at /workspace, though it does not mention the default or absolute-path handling.

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 a specific verb and resource: listing one directory inside a sandbox. It also names the fields returned (name, path, type, size), which distinguishes it from siblings like sandbox_read_file or sandbox_exec.

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 phrase 'List one directory' implies non-recursive directory listing, and the relative-path note gives useful context. However, it does not explicitly say when to use this instead of sandbox_read_file or sandbox_exec, nor does it state exclusions or prerequisites.

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