Find a symbol in 4.2BSD source

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

With no annotations, the description discloses useful behavioral details: definitions are listed first, then declarations/references, and each result appears as 'path:line: code'. This adds context beyond basic purpose, though it does not mention edge cases like not-found behavior or output limits beyond what schema provides.

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 the main verb and resource, and includes an output format example. Every word contributes value; there is no redundancy.

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?

The description covers purpose, result ordering, and output format, which is sufficient for a simple search tool with a well-defined schema and no output schema. It lacks an explicit mention of alternatives or edge cases, but the core information needed to use the tool is present.

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 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema, but the schema already documents all parameters (symbol, max_results, path_filter) with examples and bounds.

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 a specific verb ('Locate') and resource ('function, struct, macro, typedef, or variable across the 4.2BSD source'), making the tool's function unambiguous. It also differentiates from siblings like search_source by focusing on symbol lookup and mentioning result ordering.

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 use for symbol lookup, but does not explicitly state when to prefer this over sibling tools like search_source or search_all, nor does it provide when-not or alternative guidance. The context is clear but lacks explicit usage boundaries.

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