kb_exempt

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

无任何注释，描述承担全部行为披露义务。描述披露了操作范围和机制（. vaultignore 通配符、单个文件豁免、状态检查），但未披露变更的副作用，如 exempt_file 使用 frontmatter 机制会重写源文件 YAML 头部、remove_pattern 可能让原本排除的内容重新暴露给检索，也未说明修改的持久性。对无注释的变更类工具而言，行为披露有明显缺口。

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?

两句话零废字：第一句前置核心用途，第二句紧凑列举全部操作能力，与六个 action 枚举一一对应。对于多操作工具而言，篇幅控制得当且信息密度高。

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 也无注释，描述虽完整覆盖了操作空间和机制，但未说明各动作的返回行为（如 list/check 返回什么），也未提及前提条件（如知识库需先经 kb_init 注册、vault_path 何时可省略）。在一个动作多样、无输出结构的工具上，这些信息对代理人正确调用仍属必要。

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 描述覆盖率 100%，五个参数均有 detail 说明，描述未在 schema 基础上增加参数级语义。描述提到的 .vaultignore 与 single-file 豁免机制在 schema 的 method 参数中已有覆盖，因此维持基准 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?

描述明确给出动词（查看、添加、删除）和资源（知识库的 RAG 豁免项），并解释目的（排除不希望被检索的私密/草稿内容），与获取类兄弟工具（kb_search、kb_read）形成清晰区分。同时列举了与 action 枚举完全对应的六类操作，代理人无需打开 schema 即可理解工具职能。

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?

描述给出了明确的使用场景语境——管理检索豁免以排除私密/草稿内容，代理人可据此判断何时调用。但未显式点名替代工具或给出 when-not-to-use 的排除条件，例如未说明检索内容时应使用 kb_search 而非本工具。

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