search_repo

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

With no annotations provided, the description carries the burden of disclosure. It reveals that execution occurs in a sandbox and that there are limits on time and match count. This adds meaningful behavioral context beyond the tool's basic function, though it does not detail output format or error handling.

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, each providing essential information without unnecessary details. It is front-loaded with the primary purpose, and the constraints are presented in a concise, scannable format.

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?

For a simple search tool, the description covers the main behavior, execution environment, and constraints. An output schema is present, so return values are covered structurally. The only notable omission is the 'globs' parameter semantics, which prevents a perfect score.

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?

The schema has 3 parameters with 0% description coverage. The description explicitly mentions 'query' and implicitly references workspace via 'repository root', but the optional 'globs' parameter is completely unexplained. This partial coverage leaves a gap for a parameter that could affect search behavior.

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 clearly states the tool searches for a query within files under the repository root, using a specific verb and resource. This distinguishes it from sibling tools like repo_diff or run_command, which have different purposes.

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?

It provides clear context: it executes a Python script inside the sandbox and mentions limitations. However, it does not explicitly state when to use this tool over alternatives or when not to use it, though the purpose is mostly self-evident from the name and description.

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