kb_reload

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

With no annotations provided, the description carries the full behavioral burden and mostly fails it. It implies mutation/replacement of in-memory state but does not state whether the operation is expensive, blocking, safe to call concurrently, or what happens to in-flight queries or uncommitted content.

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 tight sentence with the action and its source front-loaded and zero wasted words. Appropriate size for a zero-argument operation.

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 zero-param operation with no output schema the core mechanic is conveyed, but the definition is missing the operational context an agent needs: when the reload should be triggered and what the cost or side effects are. Adequate but with clear 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?

The tool takes zero parameters, so per the rubric the baseline is 4. The schema fully describes the empty argument object and there is nothing parameter-level the description could usefully add.

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 gives a specific verb ('Rebuild') and resource ('the in-memory graph and search index from disk'), so the agent knows exactly what state is being refreshed. It is distinguishable from siblings like kb_search or kb_verify, though it never names or contrasts them explicitly.

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?

There is no when-to-use guidance at all: nothing says when a reload is necessary (e.g., after external edits to the knowledge base on disk) or when it is unnecessary or harmful. No prerequisites, no alternative tool is mentioned despite eleven siblings.

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