Semantic Search

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

The tool name and description identify a search operation, which is conventionally read-only, but the annotations explicitly declare readOnlyHint=false. The description does not explain this discrepancy, nor does it describe any state changes, permissions, rate limits, or side effects that would justify a non-read-only search operation.

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 short, but the second sentence 'Manage search operations' is vague filler that does not add actionable information. It is concise but not front-loaded with the distinctions an agent needs.

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?

There is an output schema and annotations, and the input schema has full coverage, but the description still omits critical context for a semantic search tool with seven optional parameters. It does not distinguish semantic search from lexical search or vector_search, and it leaves the non-read-only behavior unexplained despite the annotation.

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%, so the schema technically documents all seven parameters. However, those descriptions are tautological ('rrf k', 'db type', 'question'), and the tool description adds no meaning about how rrf_k, lexical_weight, semantic_weight, or number_results should be used. Baseline 3 applies because the schema coverage is complete.

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 operation, 'semantic search,' but the parenthetical '(vector_search)' is ambiguous and may collide with the sibling vector_search. 'Manage search operations' is vague and does not clearly distinguish this tool from vector_search or vector_lexical_search.

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 guidance on when to use this semantic search versus the sibling vector_search or vector_lexical_search tools. The description also gives no prerequisites, weighting guidance, or expected use context.

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