Grep the always-warm pool of top repos

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

Annotations already mark it read-only, open-world=false, and idempotent, and the description adds several behavioral details beyond those: the server keeps repos permanently cloned, results are grouped by repo and star-ranked, each group carries a handle for follow-up tools, and the pool object's syncing/ready/size indicates warming with non-final empty results. No contradiction with annotations.

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 dense but every sentence adds a distinct operational fact: scope, no-clone behavior, resource coverage, grouping/handle for follow-up, and pool-warming retry semantics. It is front-loaded with the core purpose and remains compact enough for the amount of context it provides.

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 read-only search tool with 100% schema parameter coverage, an output schema, and clear annotations, the description covers the key selection and invocation concerns: what it searches, how results are grouped, how to follow up, and when an empty result is not final. No critical operational gap is apparent.

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 coverage is 100%, so the baseline is 3 and the schema already documents query/glob/limit/max_per_repo/case_sensitive. The description reinforces that query is a substring and that grouping is by repo, but it does not add syntax or parameter-format details beyond the schema.

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 opens with a specific action ('Substring-search') and resource ('actual files of the most popular indexed home-ops repositories'), and immediately distinguishes it from 'kubesearch_grep_values' by scope. It also notes no clone step is needed, making it clear this is a pre-warmed cross-repo search rather than a repo-local grep.

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 explicitly contrasts with kubesearch_grep_values ('not just Helm values like...') and tells the agent that returned handles are intended for repo_read_file/repo_list_files/repo_grep follow-ups. It also gives retry guidance while pool.syncing is true. This is clear contextual guidance, though it stops short of an explicit 'use X instead' exclusion statement.

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