install_helm_chart

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

Annotations include destructiveHint: true, indicating potential data destruction. The description simply says 'Install,' which can be destructive (overwriting releases), but it does not elaborate on what gets destroyed (e.g., existing releases, resources) or under what conditions. It adds minimal context beyond the annotation.

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 a single, front-loaded sentence that states the core purpose without wasted words. Every part earns its place; it is appropriately sized for a tool with extensive schema coverage.

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 9 parameters (3 required) and no output schema, the description is minimally complete. It does not explain the template installation workflow, interactions between values and valuesFile, or error scenarios. While schema covers parameter details, the description leaves moderate gaps for an agent to understand full usage context.

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%, so baseline is 3. The description hints at the useTemplate parameter via 'template-based installation' but adds no further meaning beyond the schema. The schema itself already provides clear descriptions for all 9 parameters.

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 the tool's purpose: 'Install a Helm chart' with specification of both standard and template-based installation. The verb 'Install' and resource 'Helm chart' are specific, and the mention of two modes adds clarity. This distinguishes it from sibling tools like upgrade_helm_chart (upgrade) and kubectl_apply (generic apply).

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?

The description provides only implicit guidance: template mode 'bypasses auth issues.' No explicit when-to-use or when-not-to-use criteria for standard vs. template installation, nor differentiation from upgrade_helm_chart. The agent receives no clear direction on selecting this tool over alternatives.

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