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

No annotations are present, so the description carries the disclosure burden. It adds a useful behavioral caveat about folder access and page size, but it does not clarify whether the query matches file names, contents, or metadata, nor does it explain the result structure or any pagination behavior beyond the mention of page size.

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?

Two sentences, both substantive. The primary purpose is front-loaded and the caveat about access-scoped results is concise and relevant. There is no filler or redundant restatement of the schema.

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 two-parameter search tool, the description covers the core action and one important scoping behavior. However, with no output schema and no annotations, the agent is left to infer what the query matches against and what the returned results look like, which are meaningful gaps for correct invocation and result interpretation.

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?

The schema already documents the mailbox parameter well, but the query parameter has no schema description. The description adds only that the search is for files and folders matching a "text query," which provides some meaning but leaves the exact matching semantics and query formatting unspecified. At 50% schema coverage, the description partially compensates but not fully.

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 states a specific action and resource: "Search one account's OneDrive for files and folders matching a text query." This clearly differentiates it from sibling search tools like search_gdrive_items and from list_onedrive_items, since it centers on query-based search within a single OneDrive account.

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 intended use is implied by the action word "search" and the mention of a text query, but there is no explicit guidance about when to prefer this tool over list_onedrive_items or other search tools. No exclusions or alternative routing are provided, so the agent must infer when this tool is the right choice.

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