list_sandbox_files

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context beyond that. It notes the HTTP GET endpoint and which folders persist across a deep sleep, which is useful behavioral colour, but says nothing about pagination, result ordering, or behaviour when the path does not exist.

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 lines, front-loaded with the action and resource, and the HTTP endpoint is kept as a trailing implementation note. The middle parenthetical is overstuffed but not wasteful.

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?

With only two parameters and no output schema, the definition is nearly sufficient, but it never clarifies the return shape (file metadata vs names) or what an invalid path yields, and 'name' remains unexplained. Adequate but with visible gaps.

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 coverage is 50%: 'path' is documented in the schema with a default of /root, while 'name' carries no description at all. The description partly compensates by enumerating the valid folder roots, but adds no syntax or format detail for 'name'. Baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('a folder of the sandbox's files'), and the enumeration of /root, /home, /srv, /opt plus the pointer to list_sandbox_volumes differentiates it from the volume-listing sibling. The parenthetical is dense and slightly muddles the 'folders kept over a deep sleep' clause, but the core purpose is unambiguous.

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 'see list_sandbox_volumes' cross-reference implies the boundary with the volumes tool, but there is no explicit statement of when to use this vs read_sandbox_file or list_sandbox_volumes, nor any prerequisites. Usage must be inferred.

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