get_doc

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

没有 annotations，描述承担了行为披露的主要责任。描述指出返回的是完整纯文本正文，这是一个有用的行为信息；但未提及权限要求、错误场景（如 doc_id 不存在）或响应结构。对于简单读取工具而言，信息基本够用但有一定保留。

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?

描述只有两句话，第一句直接说明核心功能和输出形式，第二句给出参数格式与来源。没有冗余信息，核心内容前置，非常适合 agent 快速理解。

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?

该工具参数少、无输出 schema、属于简单的文档获取操作，描述已覆盖输入来源、输入格式和输出内容，且与兄弟工具的协作关系也已标明。对于这种复杂度，说明是完整的。

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 对 doc_id 的描述覆盖率为 100%，描述在此基础上额外补充了 doc_id 的形态示例（guides/deployment/deployment_guide）以及获取来源（search_docs/list_docs 的 id 字段），提供了超出 schema 的来源语义，能帮助 agent 正确构造参数。

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?

描述明确说明了工具的功能：获取指定文档的完整正文（纯文本），动作为“获取”，资源为“文档正文”。这与 search_docs / list_docs 的检索和列表职能明显区分，且指出了 doc_id 的来源，能够帮助 agent 准确选择该工具。

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?

描述说明 doc_id 可从 search_docs / list_docs 结果的 id 字段获取，隐含了先搜索/列表、再获取正文的使用链路。虽然没有明确写出“不要用 search_docs 获取正文”之类的排除条件，但上下文已经足够清晰。

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