Baidu List

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about read-only safety, pagination semantics (page/limit defaults), default sort order, or what happens when the directory is empty or the profile is unauthenticated. For a 9-parameter tool with zero annotation coverage this is a substantial gap.

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?

A single short sentence with no filler is structurally clean and front-loaded, but its brevity reflects under-specification rather than disciplined conciseness. It neither wastes words nor earns its place beyond the bare minimum.

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?

An output schema exists, so return-value explanation is not required, but a 9-parameter, unannotated listing tool with pagination and connection parameters needs far more than one sentence. The agent is left to infer pagination behavior, sorting, and the meaning of the NAS-related parameters.

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 only 56% and the description adds no parameter meaning whatsoever. Critical parameters like page, limit, order, and ascending have no descriptions in the schema, and the description does not compensate by explaining pagination, sort defaults, or the host/port/scheme/profile NAS-connection cluster.

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 gives a clear verb+resource: listing the contents of a Baidu Netdisk directory. An agent can tell what it returns at a glance, but it does nothing to distinguish it from closely related siblings like baidu_search, baidu_info, or file_list, so it falls short of the 5-level 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?

There is no guidance on when to use this tool versus baidu_search (querying) or baidu_info (metadata for a known path). No prerequisites, no mention of authentication or the NAS-host profile mechanism that the parameters imply.

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