upload_file

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

Annotations are mostly false, so description carries burden. It discloses the DataTransfer mechanism and a 10MB limit, but omits behavior on size exceedance, path errors, or whether it clears existing files. Adequate but not rich.

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?

One concise sentence with no wasted words. Front-loaded with the action and key details.

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 no output schema and 4 params fully described in schema, the description adds the 10MB limit and mechanism. Missing error behavior or return value, but complete enough for a straightforward 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?

Schema covers 100% of parameters with descriptions. The description adds only the 10MB limit, which is not per-parameter. Baseline 3 achieved; no additional meaning beyond 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?

The description clearly states the tool uploads a file from the server filesystem to an input[type=file] via DataTransfer, with a 10MB limit. This is specific and distinct from sibling tools like fill_form or type_text.

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 description implies usage for file inputs but does not explicitly state when to use vs alternatives or any exclusions. No 'when not to use' or alternatives mentioned.

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