Search HelmReleases

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

Goes far beyond the readOnly/idempotent annotations by disclosing substring/case-insensitive matching, grouping by chart source, ranking by public home-ops repo usage, normalization of chart_source_url, and the resolved_chart flag. This is rich behavioral context.

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?

Two compact paragraphs with the core statement first and a clearly separated note on normalization. Every sentence earns its place, though the normalization note is dense and might be overwhelming at first glance.

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 output schema and annotations, the description covers search semantics, result shape, grouping caveats, and the next-step tool to use. It provides enough detail for an agent to invoke correctly and interpret results properly.

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 covers all parameters at 100%, and the description adds real value by specifying substring/case-insensitive matching, giving query examples, and clarifying output grouping semantics. It does not add much for limit/offset, but the schema already handles those.

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?

Clearly states it searches kubesearch.dev for Flux HelmReleases / Argo Applications by chart name substring, case-insensitively. It distinguishes itself from kubesearch_get_release by noting results include an id for full details, and from image/grep siblings by its chart-name scope.

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?

Frame as 'mirrors the kubesearch.dev homepage search' with examples, and explicitly directs the agent to pass returned ids to kubesearch_get_release for full details. It does not enumerate when not to use it relative to image/grep tools, but the used context is unambiguous.

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