Get File Download URL

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial beyond that: the URL is short-lived and pre-authenticated, pdf conversion applies to Office files, small plain-text files return inline, and SharePoint requires the mcp.sharepoint App Role.

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?

Purpose and inputs are front-loaded in the first sentence with no wasted lead-in. The trailing multilingual keyword block is somewhat of a routing dump but does aid intent matching, so the cost is small.

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?

No output schema exists, so the description carries the return-value burden and does so: it specifies a short-lived pre-authenticated download URL and inline text for small files. Auth requirement for SharePoint is also covered.

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 baseline is 3, but the description adds real meaning: format=pdf converts Word/Excel/PowerPoint, and includeText behavior (small plain-text files returned inline) is explained beyond the schema's terse notation.

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?

Specific verb (Resolve/return) and resources (OneDrive/SharePoint file, download URL) with clear scope. An agent can distinguish it from files_search, which locates items rather than producing a fetchable 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?

States two concrete entry paths — a pasted link or driveId+itemId — and notes the SharePoint App Role prerequisite. It stops short of explicitly naming when to prefer files_search or files_get_download_url, but context is clear.

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