tnd_read_downloaded_chapters

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 one important behavioral limit (max 20 chapters per call) and the downloaded-only scope, but says nothing about read-only semantics, what happens when a requested chapter is not downloaded, or that oversized chapters are truncated rather than returned complete.

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 compact sentence with the resource front-loaded and the two selection modes plus the size cap packed in without filler. It is efficient, though it has no structure to separate the read mode from the limit.

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 six-parameter read tool with full schema coverage and no output schema, the description covers the essentials: what is read (chapter body text), from where (downloaded books), how to select chapters, and the batch size ceiling. Return-shape detail is partly handled by the max_total_chars/max_chars_per_chapter parameters, leaving only minor gaps.

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%, so all six parameters are already documented, including the item_ids/start_index mutual exclusivity and the 0-means-unlimited conventions. The description merely restates that same exclusivity, adding no new meaning beyond the schema, which matches the baseline of 3.

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+resource: batch-reading the body text (正文) of one already-downloaded book, and notes the 20-chapter cap. The word 批量 implicitly distinguishes it from the singular tnd_read_downloaded_chapter, but it never names that sibling explicitly, so the agent must infer the split.

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?

It clarifies that the caller can use either start_index/end_index or item_ids and that at most 20 chapters come back, which is real selection guidance. However, it gives no when-to-use guidance relative to tnd_read_downloaded_chapter, tnd_list_downloaded_chapters, or tnd_read_latest_chapter, nor any precondition such as the book needing to be downloaded first.

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