reflens_search

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

Discloses hybrid lexical+semantic search, reciprocal-rank fusion, output details (path, line range, snippet), and a security note about untrusted third-party data. No annotations exist, so description carries the burden well.

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?

Description is a single paragraph that front-loads purpose and method, then output and usage guidelines. It is efficient but slightly dense; could be broken into sections.

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 5 parameters, no output schema, and no annotations, the description covers the tool's purpose, search method, output format, recommended alternatives, and a security note. It is functionally complete for typical use, missing only edge-case details.

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 40% (descriptions only for k and diversify). The description mentions that the query should be for a 'specific symbol, string, or error' but does not explain repo, mode, or other parameters in detail, lacking compensation for low schema coverage.

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 'Search a reference repo for a SPECIFIC symbol, string, or error,' providing a specific verb and resource. It distinguishes from siblings like reflens_map by noting that for broad questions one should use reflens_map first.

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?

Explicit guidance: 'For a broad ... question, call reflens_map FIRST ... search alone is a weaker way to explore an unfamiliar repo.' Also recommends follow-up with reflens_read, giving clear context on when and how to use the tool.

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