hybrid_search

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

The description details the hybrid search process (pre-filter then rank) and expected output (list with similarity score or error), but does not explicitly state that it is a read-only operation, though implied. No annotations are present to contradict.

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 concise and well-structured: an introductory sentence, explanation, examples, syntax link, and an Args list. Every part adds value.

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?

Given the complexity, zero schema coverage, and presence of an output schema, the description covers usage, parameters, and return format adequately for an agent to select and invoke the tool 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 description coverage is 0%, but the description includes an Args section that explains each parameter, provides defaults, and gives filter expression examples, adding significant meaning beyond the schema.

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 clearly states the tool performs a hybrid search combining Redis filter expression with KNN vector similarity, and distinguishes from pure vector search by noting that using '*' as filter equals vector_search_hash.

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 explains when to use the tool (for pre-filtering before vector search in production RAG) and provides filter expression examples, but does not explicitly state when to use alternatives like vector_search_hash.

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