search_code

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

Discloses the search algorithm (BM25) and mode behavior, but no annotations are provided so the description carries full burden. Could mention read-only nature, result format, or pagination behavior. Adequate but not rich.

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?

Two concise, front-loaded sentences. First sentence states primary purpose, second adds mode specifics. No filler or redundant information.

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?

Covers core functionality and mode differentiation, but lacks information about return structure, result scoring, or how it complements/contrasts with the many sibling search tools. Given no output schema and no annotations, some gaps remain.

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%, but the description adds value for 'mode' by detailing what graph searches cover. Query and limit parameters mostly repeat schema, so marginal additional meaning overall.

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?

Clearly states it performs lexical BM25 search across indexed code chunks, with specific mention of graph mode. However, it does not differentiate from many sibling search tools (e.g., semantic_search, hybrid_search, regex_search), so not a 5.

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 guidance on when to use graph mode vs code mode, but lacks explicit context about when to prefer this tool over siblings like semantic_search or hybrid_search. No when-not or alternative mentions.

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