Helm releases

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

readOnlyHint=true already declares this a safe read, so the description doesn't need to establish safety. It adds that status, chart, and app version are surfaced, which is modest extra value, but 'Structured output' is redundant given a real output schema exists and nothing is said about scope defaults or empty-result behavior.

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 short sentences, front-loaded with the action and the key returned fields. The trailing 'Structured output' is close to wasted space since an output schema is declared, but the overall brevity is good.

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 an output schema present, the description needn't explain return shape, and the read-only annotation covers safety. What's missing is sibling differentiation in a crowded helm/kube/argo toolset, which keeps it just under a 5.

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%, and the schema already documents filter (regex), context, namespace (omit for all), and allNamespaces override. The description adds nothing beyond that, which is acceptable at full coverage.

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?

'List Helm releases' gives a specific verb and resource, and it names the fields surfaced (status, chart, app version). However, it does not distinguish itself from close siblings such as helm_status, helm_values, or helm_release_triage, so an agent must infer the boundary.

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?

No statement of when to use this versus helm_status or helm_release_triage, no prerequisites (kube context/cluster access), and no exclusions. The agent gets no routing guidance at all.

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