upload_file

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

Although annotations already flag this as destructive and non-idempotent, the description adds no behavioral context beyond those hints. It doesn't disclose whether an existing file is overwritten, whether directories are created, file size limits, or how the destination path should be interpreted.

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?

The description is a single short sentence with no filler or repetition; it is as concise as possible. The essential action is stated up front without unnecessary words.

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?

For a file upload tool with a destructive annotation and a schema that documents nothing about the parameters, the description is too thin. It omits overwrite behavior, path semantics, and any mention of the base64 payload, leaving the agent without enough context to invoke the tool reliably.

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 mentions neither 'path' nor 'file_base64' semantics. With zero parameter details in the schema and no explanation in the description, an agent cannot understand path formatting, base64 encoding requirements, or whether the destination is a directory or full file path.

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 states a specific verb ('Upload'), a resource ('a file'), and a destination ('a destination path'), making the tool's function immediately clear. It also implicitly distinguishes itself from sibling tools like download_file and delete_path, since upload is the only write-oriented file transfer operation.

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 is given for when to choose this tool over alternatives such as download_file, rename_path, or delete_path. There is no mention of prerequisites, path constraints, or exclusions, so the agent must infer usage context.

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