repo_search

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that the tool is read-only in nature ('search'), uses ripgrep, caps output ('bounded output'), and applies some form of filtering ('safety exclusions'). However, 'allowed repository' and 'safety exclusions' are undefined, and no side effects or permission requirements are discussed, which is a meaningful gap for a tool with zero annotation coverage.

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?

A single, front-loaded sentence with no filler. It efficiently communicates the core action and resource, but the vague terms 'allowed' and 'safety exclusions' could have been clarified without much extra length.

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?

Given the tool has 10 parameters, no annotations, no output schema, and zero schema description coverage, this description is far from complete. It omits parameter semantics, output format, and the concrete meaning of safety exclusions, leaving an agent unable to configure the tool correctly without additional information.

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 must compensate for 10 parameters but does not. It only hints at 'bounded output' (relating to max_results) and 'safety exclusions' (possibly path/file_glob), leaving the other parameters like pattern, word_regexp, fixed_string, context_lines, and case_sensitive unexplained.

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 states a specific action ('search'), a resource ('allowed repository'), the underlying mechanism ('ripgrep'), and distinctive constraints ('bounded output and safety exclusions'). This clearly distinguishes it from siblings like repo_tree (structure listing) and repo_read (file contents).

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?

No explicit guidance is given about when to use this tool versus alternatives. There are no usage scenarios, prerequisites, or exclusions mentioned. The only hint is the verb 'search', which weakly implies its role among the sibling tools.

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