drive_download

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

Discloses key behaviors beyond annotations: recursive download for folders, silent overwrite of existing files, failure if parent directory missing, and return value format. Annotations only have openWorldHint, so description carries full burden and does so well.

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 and well-structured. First sentence states main action, followed by necessary details and exclusion advice. No wasted 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?

Comprehensive for a download tool: covers authentication, recursion, overwrite behavior, error conditions, return value, and sibling distinctions. No output schema but description mentions return format.

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 coverage is 100%, so baseline is 3. Description adds some context (remotePath must start with '/', localPath parent directory must exist) but mostly restates schema descriptions. Marginal added value.

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 action: 'Download a file or folder from Proton Drive to the local filesystem.' It distinguishes from siblings by explicitly advising against using it for moving files (drive_move) or reading text contents (drive_read_file).

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 mentions 'Requires authentication.' Provides clear when-not-to-use scenarios with specific alternative tools. Also warns about silent overwriting and advises verifying destination.

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