Grep HelmRelease values

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

The description discloses return format (matched key path, snippet, source file), scope (every indexed HelmRelease/Application), and matching semantics (substring match). Annotations already declare read-only and idempotent, so the description adds behavioral context without contradiction, though it omits potential edge cases like rate limits.

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?

Three sentences, front-loaded with the action, containing concrete examples and essential return details. No redundant or filler content.

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 is complete for a simple grep tool: it defines the target space, matching behavior, return structure, and an external reference. Combined with the detailed schema, annotations, and output schema, nothing critical is missing.

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% with clear descriptions for all four parameters, so the baseline is 3. The description provides concrete query examples ('cert-manager.io', 'nodeSelector') that illustrate usage, but it doesn't explain limit, offset, or case_sensitive beyond what the schema already offers.

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 a specific action: full-text grep across the Helm spec.values of indexed HelmRelease/Application objects. It distinguishes itself from sibling tools (e.g., kubesearch_search_releases, repo_grep) by targeting values and returning key paths/snippets. The kubesearch.dev reference adds precise context.

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 states the tool is useful for finding real-world examples of config keys/values, which gives clear usage context. However, it does not explicitly mention when not to use it or name alternatives, so it falls just short of a 5.

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