download-drive-file

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

Annotations declare destructiveHint=false and openWorldHint=true, and the description adds genuinely new behavioral detail: without savePath the content comes back as base64 suited to small files, while savePath writes to local disk (which explains the readOnlyHint=false despite being a 'download'). It doesn't cover error behavior for invalid IDs or permission requirements.

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?

Required/optional split and front-loaded first sentence make it easy to scan, and the examples are illustrative. It is slightly longer than needed since the three examples largely restate the savePath semantics already described in prose.

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, the description correctly compensates by explaining the two return modes (saved file vs. base64) and their size implications. Combined with the prerequisite lookup tip, an agent has everything needed to invoke it correctly.

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 the baseline is 3, but the description goes beyond the schema by clarifying that savePath accepts either a directory (filename auto-detected) or a full file path, and by disclosing the implicit third behavior — base64 return when savePath is omitted — which the schema never states.

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?

States a specific verb and resource: 'Download a file from a Dooray drive,' which distinguishes it from download-attachment, download-wiki-page-file, and download-wiki-attach-file by the drive resource. It does not explicitly name those siblings, so the differentiation is implicit rather than spelled out.

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?

Gives clear operating context: required IDs, optional savePath, and a concrete routing tip — 'If you only have a file ID, use get-drive-file-meta first to get the driveId' — which points to the prerequisite sibling tool. It lacks explicit when-not-to-use guidance versus the other download tools, keeping it at 4.

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