od_download

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

With no annotations, the description carries the full burden. It does add one valuable behavioral fact not available elsewhere – the file is written to ~/Downloads/induslms – but is silent on overwrite behavior for existing files, authentication/permission needs, and failure handling for invalid ids or links.

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?

One sentence, front-loaded with the action and resource, with the destination appended. No filler.

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?

An output schema exists so return values need not be described, and the local destination is disclosed. For a one-parameter download tool this is nearly complete; the only gaps are overwrite/error semantics, which are minor here.

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 0% and the single 'target' property has no description at all. The description partially compensates by stating that target accepts an item id or a sharing link, resolving the main ambiguity, but gives no format examples or constraints.

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 a specific verb (Download) and resource (OneDrive/SharePoint file) plus the destination path, which is more than a restated name. It does not explicitly differentiate itself from the sibling download_resource, so an agent must infer the split, but the 'item id or sharing link' scope is clear.

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 phrase 'by item id or sharing link' implies the two accepted target modes, which is useful usage context, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. download_resource or od_resolve_link) to route between.

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