Baidu Info

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

No annotations are provided, so the description carries the full burden. It does disclose one meaningful behavioral trait — that the response conditionally includes a download direct link (dlink) — but says nothing about required Baidu account/auth state, read-only nature, or failure modes for invalid fsids.

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 front-loaded sentence with zero waste, and the optional dlink behavior is called out parenthetically. It is arguably too terse for a 6-parameter tool, but nothing is redundant.

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 values need not be explained, and parameter coverage is high. Still missing are the operational context an agent needs: that fsids come from baidu_list/baidu_search and any account/session prerequisite.

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 coverage is 83%, so the schema already documents host, port, scheme, profile, and fsids. The description only adds meaning for the one undocumented parameter, dlink, clarifying it yields a download direct link, which is genuinely useful but marginal.

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?

States a specific verb (查询) and resource (网盘文件详细信息), so an agent knows it retrieves metadata for existing files rather than listing or searching. It does not, however, distinguish itself from near-siblings like file_property or baidu_list, which also surface file metadata.

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 when-to-use guidance: nothing says to call this after baidu_list/baidu_search to resolve fsids, nor how it differs from baidu_download or file_download_url. The only hint at usage lives in the schema description of fsids, not in the tool description.

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