download-my-drive-item

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

Description adds meaningful details beyond readOnly/idempotent annotations: Office/PDF/TXT/CSV become text, other binaries are base64, and there is a size limit. This helps the agent predict return shape and failure mode.

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?

Two sentences with no fluff; action first, then format and limit behavior.

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?

Covers the main thing no output schema would tell the agent: representation of returned content and size bound. It doesn't state the actual MAX_DOWNLOAD_BYTES value or behavior over the limit, but for a two-parameter downloader this is near-complete.

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 already documents both parameters, so baseline is 3. The description reinforces fileName's role in extractor selection but adds little beyond what schema states, and itemId remains generic.

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 the action (download), resource (OneDrive file content), and gives concrete output-format behavior. It separates itself from metadata-oriented siblings like get-my-drive-item, although it does not explicitly differentiate from download-drive-item or get-my-drive-item-download-url.

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 when-to-use or alternative-routing guidance. The agent must infer from the name/title that this is the content-fetching counterpart to get-my-drive-item-download-url and download-drive-item.

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