upload_file

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

No annotations are provided, so the description carries the full behavioral burden and delivers nothing. It does not say whether the selector targets an <input type=file>, whether the upload is triggered immediately or deferred to a form submit, whether multiple files are supported, or what happens on failure.

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 words is short but this is under-specification rather than conciseness; there is no substantive content to be front-loaded. Brevity here costs the agent all actionable information.

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?

A two-parameter tool with 100% required params, zero schema descriptions, no annotations, and no output schema gets essentially no documentation. The definition is wholly inadequate for correct invocation.

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 0% and the description adds nothing. It never explains what 'selector' identifies or what form 'files' takes (string vs array, local path vs URL vs base64), despite the schema's oneOf union making this ambiguity acute.

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?

"File upload" merely restates the tool name with no verb+resource specificity beyond the obvious. It does not distinguish this tool from siblings like 'fill', 'set_storage', or 'eval', which could also plausibly feed data into a page.

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?

No guidance whatsoever on when to use this tool, what prerequisites exist (e.g. a file input must already be located/focused), or how it relates to alternatives. The agent is left to guess entirely.

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