List selectable Baidu files

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the numbered-list output and selection-expression usage, but does not disclose authentication needs, default directory behavior, sorting, pagination, rate limits, or side effects. This is a significant gap for a tool with no other structured behavioral context.

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, front-loaded sentence with no wasted words. It is concise and immediately states the core function, though it could be longer to cover necessary parameter and usage context.

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 five optional parameters, no annotations, no output schema, and no sibling differentiation, the description is too sparse. It does not explain parameter semantics, return format beyond 'numbered list', or how this tool fits into the selection workflow. The tool is functional but incomplete for an agent to use 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 5 parameters with 0% description coverage, and the description does not explain any of them (dir, limit, category, fileTypes, recursive). The description only talks about output and selection expressions, adding no meaning to the parameters themselves.

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 a specific verb and resource: 'List files and return a numbered list that can be selected with expressions like 1,3,5-9.' This distinguishes it from plain listing tools like baidu_list_files by emphasizing the selectable numbered output.

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 implies the tool is used when a numbered, selectable list is needed for selection expressions, but it does not explicitly state when to use it versus siblings like baidu_search_selectable_files or baidu_list_files. There is no exclusion or alternative mention, so usage context is only implied.

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