code_search

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

Discloses the environmental dependency and mode behavior. As a search tool, it is implicitly read-only, and no annotations are provided. The description adds context beyond the schema.

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?

Extremely concise, front-loading the purpose in the first sentence and adding the dependency in the second. No 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?

Despite three parameters, the description lacks details on return format, pagination, regex behavior, and what fields are searched. For a search tool, more completeness is expected.

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?

With 0% schema description coverage, the description should compensate but does not explain individual parameters (query, regex, max_results). It only implies query is the search term, leaving agents to infer the rest.

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?

Description clearly states it performs lexical search over HICAR source (.F90 files) and documentation, differentiating it from sibling tools like semantic_search which probably do semantic search.

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 mentions the dependency on HICAR_REPO environment variable for source searches and the fallback to docs-only in bundled mode, giving clear guidance on when it works and under what conditions.

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