Download SharePoint File

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

With no annotations provided, the description carries the burden. It discloses that output is base64 and that the response is limited to 10 MB, which is useful. However, it does not specify error behavior for files exceeding the limit, authentication requirements, or confirm read-only nature, leaving some behavioral gaps.

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 two primary sentences plus a localized intent section. The main purpose is front-loaded and the 10 MB limitation is an important caveat presented early. The Chinese intents add slight redundancy but remain compact.

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 download tool with two parameters and no output schema, the description covers the essential purpose, return format, and critical size limitation. It omits explicit differentiation from drive_download_file, but the name and sibling list help. The 10 MB limit is a crucial operational detail that makes it practical.

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 100% (both itemId and driveId have descriptions). The tool description adds no parameter-specific explanation beyond what the schema already provides, so the baseline of 3 is appropriate.

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') with a specific resource ('a document-library file') and output format ('as base64'). This distinguishes it from sibling tools like drive_download_file which targets OneDrive files, while the Chinese intent section reinforces the SharePoint scope.

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 implies usage for downloading SharePoint document library files and notes the 10 MB response limit, which is a key usage constraint. However, it does not explicitly state when to use this tool over drive_download_file or mention any alternatives for files larger than 10 MB.

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