Recursively list Baidu files

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It only mentions optional recursion, but fails to disclose pagination, output format, cost implications of recursion, or authentication requirements.

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 single sentence is concise but under-specified for a tool with 10 parameters. It lacks structure that would group or explain the optional filters, and the brevity results in missing critical usage details.

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?

With no output schema, the description should at least indicate what the returned list contains, but it does not. Given the complexity of the schema (10 params) and absence of annotations, the description is far from complete.

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 0%, and the description does not compensate. None of the 10 parameters (e.g., web, ctime, order, deviceId) are explained beyond their raw names and types, leaving the agent unable to correctly construct calls.

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 tool lists files below a Baidu Netdisk path, with an explicit optional recursion flag. The title 'Recursively list Baidu files' and name 'baidu_list_all_files' differentiate it from the sibling 'baidu_list_files', which likely lists non-recursively.

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?

Usage is implied: use this to list files at a given path, optionally recursively. However, no explicit guidance is provided on when to prefer this over baidu_list_files, baidu_search_files, or other siblings, nor any exclusions.

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