Helm release triage

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real value by disclosing aggregation behavior and the shape of the synthesis (likely causes, suggested next commands, recent-revision evidence). It omits what happens on a missing/unhealthy release or whether diagnosis is bounded in scope.

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?

A single dense sentence with no filler, leading with the core capability and then enumerating exactly what comes back. Nothing to trim.

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?

An output schema exists so return values need no explanation, and the inputs are fully documented. The remaining gap is behavioral edge cases: what the agent gets if the release doesn't exist or if helm isn't reachable, which for a diagnostic tool would matter.

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 all three parameters (context, release, namespace) are documented in the schema, including the namespace default. The description adds no semantics beyond that, which is the baseline case when structured fields do the work.

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?

Specific verb ('Diagnose') plus resource ('a Helm release's health') and an explicit statement that it fuses helm status + helm history into one composite result. That implicitly separates it from the sibling helm_status, though no sibling is named outright.

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?

'in one call' hints that this replaces manually running helm_status and helm_history, but the description never states when to prefer it over helm_status or helm_list, nor any preconditions (e.g. release must exist, namespace must be in context). Usage is inferable rather than stated.

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