search_knowledge

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

Annotations already declare readOnlyHint=true, and the description supplements this with useful behavioral detail: all domains are searched at once and results are fused via RRF for fair interleaving. This goes beyond the structured annotation without contradicting it.

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 two tight sentences: the first states the core behavior, and the second gives a usage criterion and concrete example. There is no filler, fluff, or repetition of schema/annotation details.

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?

It is adequately complete for tool selection: it says what the tool searches, how it combines results, and when to use it. However, the shape has 5 undocumented parameters and an output schema, so an agent still lacks detail on what symbols/category/repository constrain and what an RRF fusion result looks like

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 parameter description coverage is 0%, so the description carries the burden of documenting parameters, but it never mentions limit, symbols, category, or repository. Only 'query' behavior is implied through 'Search ALL domains...', leaving agents to guess what the optional filters do.

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 opens with a specific verb and clear scope: 'Search ALL domains (VHDL, documentation, code) at once'. It also names a concrete behavior, RRF fusion, which distinguishes this tool from domain-specific siblings like search_docs and search_code.

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 description gives explicit guidance: 'Use when the question may span domains' and provides a realistic cross-domain example. It does not explicitly name the domain-specific alternatives or say when not to use this tool, but the intended use case is conveyed clearly enough.

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