Reads the status of a download batch and returns the current batch when no batch ID is supplied. Use it to check progress or completion of grouped download tasks.
读取离散下载批次状态；不传 batch_id 时返回当前批次。
| Name | Required | Description | Default |
|---|---|---|---|
| batch_id | No | 可选批次 ID |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral burden. It discloses that this is a read operation and explains the default-current-batch behavior, but it does not describe permissions, error behavior, or what the returned status contains.
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 redundant wording. The default behavior is included efficiently after the main purpose.
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?
For a simple one-parameter read tool this is adequate to invoke correctly, especially because the schema documents the parameter fully. However, without an output schema, the description does not explain what status information is returned or how errors are represented.
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 100%, so the parameter is already documented. The description adds meaningful semantics beyond the schema by stating that when batch_id is omitted, the current batch is returned.
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 states a specific verb and resource: reading discrete download batch status. It is distinguishable from general status or job tools by the word 'batch', but it does not explicitly name siblings like tnd_get_status or tnd_get_jobs.
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 by the purpose of reading batch status, and the description notes that omitting batch_id returns the current batch. However, it does not say when to use this instead of tnd_get_status, tnd_get_jobs, or tnd_get_book_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.