onedrive_search

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

Annotations already establish that this is a read-only, idempotent, open-world operation. The description adds the useful scope that search is by file or folder name, but it does not explain matching behavior, authorization requirements, pagination, or other runtime traits. Given the annotation coverage, this is adequate but minimal.

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 definition is a single front-loaded sentence with no wasted language. It communicates the core operation efficiently.

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 read-only search tool with full schema descriptions and annotations, the definition is enough to invoke the tool correctly. It is less complete for routing decisions because it does not contrast with sibling OneDrive listing and reading tools.

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 the query, limit, and access_token parameters are already documented. The description's 'by name' wording reinforces the query parameter's meaning but adds no syntax, matching rules, or format details beyond the schema.

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 verb and resource: search OneDrive files and folders, narrowed to name-based search. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as onedrive_list or onedrive_read.

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 name' implies that this tool is for name-based lookup rather than listing or reading a known item. However, it gives no explicit guidance on when to use it instead of onedrive_list, onedrive_read, or other OneDrive operations.

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