Read selected 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. It discloses a local cache side effect, parsing of supported formats, and the return of chunked text, which is useful. However, it omits important behaviors such as auth requirements, what happens with unsupported file types, error behavior, and whether the cache persists or is cleaned.

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 that efficiently communicates the core purpose and output. Every word adds value, with no fluff or repetition.

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 absence of an output schema and annotations, the description provides a basic understanding but lacks completeness. It does not specify the format of the chunked text, the list of supported document formats, prerequisites (e.g., that a selection must exist), or error conditions. For a read tool, this is minimal but not wholly inadequate.

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%, so the description must compensate. It does not explain `selectionId` (beyond the vague 'selected files') or `chunkSize` (only hints at chunking via 'chunked text'). This is insufficient for an agent to understand how to set parameters correctly.

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 action (`Download selected files to local cache, parse supported document formats, and return chunked text`) with a specific resource (`selected files`) and distinguishes itself from siblings like `baidu_download_file` (raw download) and `baidu_analyze_selection` (analysis) by explicitly focusing on parsing and returning text chunks.

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 explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like `baidu_download_file` or `baidu_analyze_selection`. Usage is only implied by the phrase 'selected files', which suggests it should be used after a selection exists, but this is not explicit.

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