browser_file_upload

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

Discloses key behavior (upload and cancellation) but no annotations present. Lacks details on prerequisites, error handling, or authentication needs. Adequate but not exhaustive.

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?

Concise docstring with purpose first, then parameter and return info. No wasted sentences, clear structure.

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?

Given output schema exists, return explanation not needed. But description omits error states (e.g., dialog not present, invalid paths) and constraints. Could be more complete for a file upload tool.

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 fully explains the 'paths' parameter: absolute paths, single/multiple, and meaning of omission. Adds significant value 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?

Clear verb 'upload' and resource 'files', specific context 'when a file chooser dialog appears' distinguishes from sibling tools like browser_click or browser_type.

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?

Explicitly states when to use (file chooser dialog) and what happens if paths omitted (cancellation). Lacks explicit exclusion of non-dialog contexts, but context is sufficiently clear.

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