drive_upload

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

The description adds behavioral context such as requiring user confirmation and the default folder behavior when folder_id is omitted. While annotations (destructiveHint=false) suggest it is not destructive, the description does not contradict them and provides additional useful information.

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 concise with three focused sentences: purpose, condition, and return value. No unnecessary words; each sentence adds value.

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 simple upload tool, the description covers key aspects: purpose, user confirmation, default folder, and return value. It lacks details on local_path and name semantics but is sufficient for typical use.

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?

The description partially compensates for the 0% schema description coverage by explaining the folder_id parameter's behavior when omitted. However, it does not add meaning for local_path or name beyond their names, leaving some ambiguity.

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 'Upload a local file to Drive,' which is a specific verb+resource combination. It distinguishes from sibling tools like drive_search, drive_list, and drive_delete by focusing on the upload action.

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 mentions 'Requires user confirmation before calling,' providing important usage context. However, it does not specify when not to use this tool or suggest alternatives, so it falls short of a perfect score.

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