search_codebase

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

With no annotations, the description carries the full burden. It mentions a token ceiling safeguard, hinting at a limit, but does not detail behavior when the limit is reached or confirm read-only nature. The semantic query aspect is stated but not elaborated.

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 a single sentence that is concise and front-loaded with the core action. It earns its place without unnecessary words, though more structure could improve clarity.

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?

Although an output schema exists, the description lacks context on prerequisites (e.g., the codebase must be indexed), the meaning of 'isolated', and parameter interplay. With 5 parameters, the description is too brief to be fully informative.

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%, so the description needs to compensate. However, it adds no parameter-specific details beyond the high-level purpose. The parameters repo_path, query, limit, file_filter, token_budget are not explained in the description.

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 uses specific verbs and resources, stating it performs semantic queries on code blocks from an isolated indexed codebase path with a token ceiling safeguard. This clearly differentiates it from sibling tools like search_all_codebases, which searches across all codebases.

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 implies usage for a single isolated codebase path, but does not explicitly state when to use this tool versus alternatives like search_all_codebases. No when-not-to-use guidance is provided.

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