search_knowledge

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

Annotations already cover read-only and non-destructive hints. The description adds valuable context: fast BM25 lexical search, no LLM call, no quota cost, and explicitly 'Read-only, no side effects.' This goes beyond the annotation basics, though it doesn't detail result structure or pagination, which is acceptable given the tool's simplicity.

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?

Three sentences, each earning its place: functionality, usage timing, and alternative. Front-loaded with the core purpose, then key behavioral notes. No fluff or repetition of schema fields.

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 read-only, two-parameter tool with no output schema, the description covers purpose, when to use, performance characteristics, safety, and alternative tool. It is sufficiently complete for an agent to select and invoke correctly.

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 coverage is 100%, so the baseline is 3. The description adds meaning by explaining the query is a natural-language question about specific topics (MCP tools, response shapes, etc.), and reinforces the limit as controlling 'ranked results'. This is more than the schema alone provides.

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 uses a specific verb ('Returns') and resource ('AlgoVault knowledge bundle') with clear scope: ranked snippets answering questions about MCP tools, response shapes, integration patterns, or code examples. It also explicitly distinguishes itself from sibling chat_knowledge by noting that chat_knowledge provides synthesized natural-language answers.

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?

Provides explicit when-to-use guidance: 'Call this BEFORE other tool calls to confirm parameter usage and avoid hallucinating tool shapes.' Also names the alternative: 'For a synthesized natural-language answer use chat_knowledge.' This gives clear context and exclusions.

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