codebase_search

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

With no annotations, the description implies read-only behavior by saying 'returns relevant code chunks', but does not explicitly state it is non-destructive or discuss other behavioral traits like rate limits or authentication.

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 sentences, front-loaded with purpose and a critical usage instruction, making it highly efficient and easy to parse.

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?

Despite complex configuration (7 parameters), the description lacks output format details; it only says 'returns relevant code chunks' without describing the response structure, which is needed since no output schema is provided.

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%, so the description adds little beyond what parameters already convey; it merely restates 'natural language query' and 'relevant code chunks' without new semantic detail.

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 it performs semantic search across an indexed codebase using natural language queries, distinguishing it from other tools like codebase_index or codebase_symbol.

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?

Explicitly instructs to only use after codebase_index is complete and to check codebase_status first, providing clear context for when this tool is appropriate, though it does not mention alternatives.

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