trawl_search_repo

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the bare action: no read-only confirmation, no ranking/relevance behavior, no result volume defaults, no pagination. The only implicit signal is that "search" is a non-mutating operation.

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 zero waste, but the brevity stems from omission rather than efficiency. It is adequately tight without being informative.

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?

With five parameters, no annotations, and no output schema, the description should explain scoping (repo vs pool), what chunk_types filtering does to results, and roughly what comes back. None of that is present, so an agent cannot confidently choose this over sibling search tools.

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 all five parameters (query, top_k, pool_name, repo_name, chunk_types) are already documented in the schema. The description adds no meaning beyond that, which is the baseline 3 case.

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 verb+resource ("search" + "within a specific repository"), which is more precise than a generic search. However, it does not distinguish this from the many near-identical siblings (trawl_search_pool, trawl_search_code, trawl_search_multi, trawl_search), leaving the agent to infer the scope difference from the name alone.

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?

There is no statement of when to use this versus trawl_search, trawl_search_pool, or trawl_search_code, which is a critical gap given roughly six overlapping search siblings. The word "specific" hints at scoping but no explicit selection condition is given.

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