onedrive_search_files

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

No annotations provided; the description only adds 'recursive' behavior. It fails to disclose that no search parameters (name, directory) can be passed, contradicting the semantics implied by the description.

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?

Single sentence, 9 words, efficient. But the lack of details about the missing parameters reduces its practical value. Could be slightly longer to clarify the discrepancy.

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?

The description is incomplete for a tool with no parameters and no output schema. It does not explain how the agent can specify a search term or directory, or what the tool searches by default.

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?

With 0 parameters and 100% schema coverage, baseline is 3. However, the description introduces concepts (name, directory) not reflected in the schema, misleading the agent about what can be specified. No parameter documentation exists.

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 (search files by name) and resource (OneDrive directory) with recursive behavior. However, the input schema has no parameters, making the described functionality impossible to specify via arguments, which confuses the agent.

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 tool versus siblings like onedrive_list_files or onedrive_file_info. The description does not mention prerequisites, scope, or limitations.

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