sp_drive_file_version_get

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

Annotations already provide readOnlyHint and idempotentHint, but the description adds important behavioral context: 'does NOT acquire a checkout, does NOT modify SharePoint state' and mentions saving to a local temp file. No contradictions with 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?

Very concise: two sentences, no fluff, front-loaded with the primary action. Every sentence adds value.

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 2-parameter read-only tool with an output schema, the description provides enough context: return value (absolute path), prerequisite step, and read-only guarantee. Minor omission: no error handling or format details, but acceptable given simplicity.

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?

With 0% schema description coverage, the description should explain parameters. It only indirectly clarifies version_id by referencing sp_drive_file_history, but does not explain 'url' (expected format or scope) or provide any syntax details. This is insufficient.

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?

Description clearly states the verb 'Download', the resource 'historical version of a SharePoint file', and the outcome 'Returns the absolute path'. It also implicitly distinguishes from sibling tools like sp_drive_file_history (which finds version_id) and sp_drive_file_read (reads current version).

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?

Explicitly instructs to 'Use sp_drive_file_history first to find the version_id you want', providing a clear prerequisite. Also states the read-only nature, setting expectations for when to use this tool.

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