Retrieve local summary information for a downloaded book by book ID without returning full chapter text. Use it to check a book's downloaded status and metadata before reading or managing chapters.
读取某本已下载书籍的本地摘要信息，不返回完整章节正文。
| Name | Required | Description | Default |
|---|---|---|---|
| book_id | Yes | 数字书籍 ID |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits: the data is local (本地) and the response excludes full chapter text. However, it never says what the summary contains, whether a download prerequisite must be satisfied, or how it behaves for a book that was never downloaded.
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 sentence with two purposeful clauses: the primary action is front-loaded and the exclusion clause follows immediately. Nothing is redundant and no words are wasted.
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?
The tool is simple (one required parameter, no nested objects, no output schema), so little explanation is needed. Still, with no output schema the vague term '本地摘要信息' leaves the agent unsure what fields come back, and the not-downloaded case is unaddressed.
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 100% with a single required book_id already documented as a numeric book ID. The description's phrase '某本已下载书籍' only reinforces that the ID must refer to a downloaded book, adding marginal meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.
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 concrete verb+resource: read the local summary info of a downloaded book. It also draws one boundary by saying it does not return full chapter body text, which separates it from the read_downloaded_chapter* siblings. It does not distinguish itself from near-neighbours like tnd_get_status, tnd_check_chapters or tnd_preview_book, so sibling differentiation is only partial.
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 rather than stated: an agent can infer this is for inspecting an already-downloaded book's metadata without pulling chapter content, and the 'does not return full chapter body' clause implicitly routes content reads to the read_downloaded_chapter* tools. There is no explicit when-to-use/when-not-to-use statement and no mention of what happens if the book is not downloaded.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.