search

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

No annotations are provided. The description adequately describes the tool's read-only behavior (searching and returning results) but does not explicitly state it is non-destructive or mention any rate limits or auth requirements.

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?

Three concise sentences that front-load purpose and provide mode guidance without extraneous detail. Every sentence earns its place.

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 query types, modes, filters, source, and limit. Mentions result format. Lacks explicit mention of result ordering or behavior when source is absent, but is largely complete for a search tool.

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?

All parameters have descriptions in the schema (100% coverage), so the description adds only marginal value beyond syntax and domain specifics like 'formatted text for context injection.'

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 the tool searches a codebase using natural-language, code, or exact-symbol queries. The verb 'search' and resource 'codebase' are specific, and it distinguishes from sibling tools like get_chunk or find_related.

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 explicit guidance on when to use hybrid, bm25, or semantic modes, and mentions filters to narrow results. However, it does not discuss when to avoid this tool in favor of alternatives like find_related.

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