download-drive-item

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

Annotations already mark the operation as read-only, idempotent, and non-destructive, and the description adds valuable runtime behavior: specific file types are converted to text, other binaries are returned as base64, and the result is size-limited by MAX_DOWNLOAD_BYTES. This meaningfully goes beyond the annotation hints, though the exact behavior when the size limit is exceeded is not disclosed.

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 three short sentences with the core action front-loaded, followed by the conversion behavior and the size limit. Every clause adds distinct information with no redundant wording, making it easy for an agent to scan.

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 reasonably explains the main return forms (text vs base64) and the size limit, which is essential for deciding how to handle the result. It leaves gaps around the exact response envelope, error conditions, and what happens when MAX_DOWNLOAD_BYTES is exceeded. These are material omissions for a tool that returns arbitrary file content.

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 input schema describes all three parameters, so the baseline is 3. The description adds meaningful context for the optional fileName parameter by mentioning text extraction, which explains why the filename helps pick the right extractor. It does not, however, add real semantic value for driveId or itemId beyond the schema's generic 'Value for driveId/itemId' text.

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 states a specific action ('Download a file's content from SharePoint') and distinguishes the tool from nearby siblings like get-drive-item by specifying that the output is either converted text or base64-encoded binary. However, it does not explicitly differentiate from download-my-drive-item, leaving some ambiguity about which drive context applies.

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?

No explicit guidance is given for when to use this tool versus the closely related siblings download-my-drive-item, get-drive-item, or get-my-drive-item-download-url. The phrase 'from SharePoint' implies a SharePoint drive as opposed to a personal OneDrive, but the description does not state that contrast or mention any alternative tools.

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