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

Beyond the read-only annotations, the description discloses that the tool is fast, never quota-gated, and returns a specific items structure. It also explains that hybrid mode combines vector cosine and keyword search, adding useful behavioral context.

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?

The description is front-loaded, dense, and free of filler. Every sentence contributes useful information about parameters, behavior, or return shape.

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?

With no output schema, the description still supplies the return shape and covers all parameters and core behavior. The only notable gap is explicit guidance on when to choose this tool over related retrieval or document-fetch tools.

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 0%, so the description carries the full burden and does so effectively. It explains query as natural language, collection_id as scoping, top_k range and default, and mode enum values including the default hybrid behavior.

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 states a specific verb and resource: search the caller's knowledge base and return relevant chunks. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as kb_get_doc or search_personal.

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?

It tells the caller to provide a natural-language query and explains optional scoping and mode selection, which implies the intended retrieval use case. However, it does not state when to use this tool instead of alternatives like fetching a specific document or searching other domains.

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