onedrive_write_file

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

With no annotations, the description must fully disclose behavioral traits. It only states 'writes text content' but omits critical details such as whether it overwrites, appends, or creates files, what permissions are required, and how file destination is determined.

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?

The description is a single concise sentence with no redundancy, but it omits critical information, making it more insufficient than efficient.

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 zero-parameter schema and lack of output schema, the description should explain how the agent specifies the file and content. It does not, leaving the tool's usage ambiguous and incomplete.

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?

Although the input schema has zero parameters (100% coverage), the description adds no meaning beyond the bare action. It fails to clarify that the tool likely relies on implicit state (e.g., previous file selection), leaving the agent without essential context.

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 clearly states the action ('writes text content') and the resource ('a file in OneDrive'), distinguishing it from sibling tools like onedrive_read_file or onedrive_delete_file. However, it lacks specificity about overwriting vs. creating files.

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 description provides no guidance on when to use this tool versus alternatives or any prerequisites (e.g., authentication, file path specification). Given the zero-parameter schema, the agent is left guessing how to indicate the target file and content.

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