kb_rebuild

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

With no annotations, the description carries the full burden. It discloses the destructive/heavy nature of the operation ('删除磁盘缓存' and '强制全量重建索引'), warning the agent that this is not a lightweight read. It omits details like permissions or time cost, but the core behavioral profile is clear.

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?

One sentence, front-loaded with the action, and the usage condition is isolated in a parenthetical. No wasted words.

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 single-optional-param maintenance tool with no output schema, the description covers the operation and its trigger conditions. It doesn't describe return values or failure modes, but these are less critical for a destructive rebuild action where the effect is the point.

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% and the vault_path property is fully documented in the schema (optional, absolute path, condition for omission). The tool description adds no additional parameter semantics, so a baseline of 3 is appropriate.

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 names a specific action — deleting the knowledge base's disk cache and forcing a full index rebuild — with a clear resource ('指定知识库') and scope. This distinguishes it from siblings like kb_init (initialization) and kb_search/kb_read (query operations).

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?

The parenthetical '(首次建库或内容大改后用)' explicitly states when to invoke the tool: after initial database creation or major content changes. It does not name alternatives or when-not-to-use conditions, so it stops short of a 5.

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