kb_chapter

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

无 annotations，描述需承载全部行为说明。仅说明了返回内容，但未提及权限、副作用、是否缓存、最大字符限制行为等。'读单章'暗示只读，但未明确安全性或错误处理。

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?

极简一句话，前置动词和返回内容，无冗余信息。

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?

对于 3 参数、无输出 schema、无 annotations 的工具，描述仅提供了基本用途。缺少参数说明、使用场景和只读保证，但核心功能清晰。

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?

3 个参数，schema 描述覆盖率仅 33%（仅 chapter 有描述）。description 未补充 subject 和 max_chars 的语义（例如 subject 是分类还是过滤条件，max_chars 如何影响输出）。在低覆盖率下，描述未起到补偿作用。

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?

明确说明动词和资源：读取单章并返回章节全文与结构化原子/组合行。能区分于 kb_overview、kb_search、kb_atoms 等兄弟工具（后者侧重概览、搜索或原子），但未提及其与 kb_atoms 的边界。

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?

没有说明何时使用本工具而非 kb_atoms 或 kb_search，也没有前提条件或排除场景。用户只能假设当需要完整章节内容时使用，但描述未明说。

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