Auto-Browser

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

No annotations provided, so description carries full burden. It fails to disclose: what 'captured' means (active monitoring vs history), persistence behavior, return format/structure, or whether this is read-only. 'Captured' hints at statefulness but doesn't explain the mechanism.

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?

Single 9-word sentence with zero waste. Front-loaded with action verb ('List'), followed by resource and scope. Every word earns its place.

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?

Minimal but viable for a single-parameter tool. Missing description of return values (no output schema exists to compensate), which would help the agent understand what data structure to expect from the download listing.

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 0% schema description coverage, the description partially compensates by mentioning 'one session' which maps to the session_id parameter. However, it omits format details or where to obtain the ID (e.g., from browser.create_session), which is critical given the schema lacks descriptions entirely.

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 uses specific verb 'List' with clear resource 'files captured from browser downloads' and scope 'for one session'. It effectively distinguishes from siblings like browser.list_sessions (lists sessions) and browser.list_tabs (lists tabs).

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?

Implies usage context via 'for one session' (indicating session_id is required), but lacks explicit guidance on when to use this vs checking other sources, prerequisites (e.g., downloads must be captured first), or workflow sequencing.

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