OneDrive Files

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that: no mention of pagination, how 'shared' interacts with other params, or what item_id returns (download URL vs listing). With annotations carrying the safety profile, the description should still contribute operational detail and does not.

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?

A single, front-loaded sentence with no waste. It could be slightly richer given five parameters, but it earns its place and is not padded.

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?

Five parameters, no required fields, no output schema, and no annotations beyond read-only hints. Ambiguity around which param combination is valid (e.g., search vs shared vs item_id) is left entirely unexplained, so an agent has to guess the mode-selection logic.

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 100%, so each parameter already has an explanation. The description's 'browse or search' hints at path/search modes but doesn't add syntax, mutual exclusivity, or precedence rules beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a verb (browse or search) and resource (OneDrive files), which is clear enough on its own. But it doesn't distinguish this from sibling tools like ms_sharepoint or ms_search, which also surface file/content search. A minimally viable but non-differentiating statement.

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 guidance on when to use this over siblings like ms_sharepoint or ms_search, and no mention of prerequisites such as a path or item_id. The description just states both modes exist without conditions for either.

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