List Browser Files

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

No annotations exist, so the description carries the full burden, and it discloses several non-obvious traits: the sandbox is ephemeral (files vanish when the browser dies), a CDP download-path prerequisite exists, and there is a race between downloadProgress "completed" and file readability with retry advice. It omits what happens on a nonexistent path or permission errors.

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?

Four short sentences, front-loaded with the operation and default, then prerequisites and the timing caveat. Nearly every sentence earns its place; the redundant restatement of the default path slightly overlaps with the schema.

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?

There is no output schema, so the description should hint at the return shape; it says files are discovered but never indicates whether entries are names, paths, or sizes. Everything else an agent needs to call it correctly — location, prerequisite, retry behavior — is present.

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 100%, including the default (/tmp/downloads) for path, so the schema already does the heavy lifting. The description reinforces the default path but says nothing about the glob `pattern` parameter or how results are ordered, adding no meaning beyond the schema.

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 and resource ("List files inside the browser sandbox") with the default location, so the operation is immediately identifiable. It does not explicitly contrast with the closest sibling, get_browser_file_url, though the scope difference (listing vs. retrieving a URL) is implied.

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?

Gives clear situational guidance: "Use after a download completes to discover what was saved," plus the prerequisite of pointing downloads at /tmp/downloads via CDP Browser.setDownloadBehavior. It does not name an alternative tool or a when-not condition, but the context for invoking it is unambiguous.

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