nworks_drive_download

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

Excellent disclosure despite no annotations: specifies OAuth authentication requirement with exact scope (file.read), explains side effects (local file creation when outputDir set), details return format variations (text vs base64), and discloses the 5MB size constraint that limits direct content return. Fully compensates for missing annotations.

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?

Three tightly constructed sentences with zero waste: purpose declaration, auth requirements, and behavioral constraints/return modes. Information is front-loaded and every clause earns its place.

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?

Despite no output schema, comprehensively covers return behavior (encoding types, file vs. content), authentication prerequisites, and operational constraints (5MB limit). Sufficient for an agent to predict outcomes and handle errors 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?

While schema has 100% coverage, the description adds crucial semantic context about how outputDir interacts with file size (5MB limit) and return encoding (text vs base64), which is not fully captured in the schema's basic parameter descriptions. Elevates understanding beyond raw schema definitions.

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 specific verb (다운로드/download) and resource (드라이브 파일/drive file) clearly. However, it does not explicitly distinguish from sibling tools like nworks_drive_upload or nworks_drive_list (e.g., 'use this to retrieve files after listing them with nworks_drive_list').

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?

Provides explicit operational guidance on when to use outputDir (files >5MB must use it, otherwise content returned directly) and explains the dual return modes (file save vs. content return). Lacks explicit comparison to alternative tools (siblings), but clearly defines the critical 5MB threshold for successful invocation.

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