Upload Small OneDrive File

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

Without annotations, the description effectively discloses key behavioral context: it requires delegated Files.ReadWrite permission and is intended for small files (implying size limitations). It does not mention overwrite/rename behavior or response format, but the schema covers conflictBehavior and the tool's purpose is not misrepresented.

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?

Three concise sentences: purpose, size limitation/alternative, and permission requirement. The Chinese intent list is a useful add-on for multilingual agents and does not bloat the description. Front-loaded with the tool's primary function.

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?

Given the tool's moderate complexity (5 params, no output schema) and lack of annotations, the description covers the essential context: what it does, when to use it, and required permissions. It omits the return value and exact size limit, but the schema and the small/large distinction provide adequate guidance for an agent.

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 parameters are fully documented in the schema. The description adds no extra parameter meaning beyond what the schema already provides (e.g., it doesn't explain the 'small' size threshold or clarify base64/text modes beyond schema definitions). Baseline 3 is appropriate.

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?

Clearly states 'Upload a small file to the signed-in user OneDrive' with a specific verb (upload), resource (file to OneDrive), and scope (signed-in user). Contrasts with large-file upload sessions and identifies the target as OneDrive vs SharePoint, distinguishing it from siblings.

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 guides on when to use this tool ('small file') and when not ('Use upload sessions for large files'), providing an alternative. Also notes the required delegated permission (Files.ReadWrite), which is a prerequisite.

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