Search Baidu files

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the search action. It does not mention pagination behavior (page/num), what happens when recursion is enabled, result format, auth requirements, or any default limitations.

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 that is front-loaded with the key action and target. It has no wasted words, though it is minimal to the point of under-specification.

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 complexity (8 parameters, no output schema, no annotations), this one-sentence description is grossly inadequate. It does not clarify pagination, recursion behavior, category filtering, or the distinction from the selectable-file search sibling, so an agent cannot invoke it confidently.

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 input schema has 8 parameters with 0% description coverage, and the description only adds meaning for 'key' via the phrase 'by keyword'. No explanation is given for 'dir', 'recursion', 'category', 'web', 'deviceId', 'page', or 'num', leaving their semantics unclear.

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 uses a specific verb and resource: 'Search Baidu Netdisk files by keyword.' It clearly communicates this is a search operation, distinguishing it from list/delete/upload siblings. However, it does not differentiate from the similarly named 'baidu_search_selectable_files' sibling, so it lacks full sibling differentiation.

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 like 'baidu_list_files' or 'baidu_search_selectable_files'. It does not state any prerequisites, exclusions, or context for choosing this search tool.

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