install_helm_chart

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

Annotations already signal destructiveness. The description adds the template-based installation behavior, which is useful, but does not expand on other behaviors like namespace creation default or potential side effects.

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, clear sentence that front-loads the core action. It is appropriately concise, though could incorporate a bit more detail without becoming verbose.

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 no output schema, the description does not explain return values or installation outcomes. It lacks prerequisites (e.g., kubeconfig) and context about the two installation modes. For a complex tool with 9 parameters, more context is needed.

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%, so the description adds little beyond the schema. It mentions standard vs. template-based installation, which relates to the 'useTemplate' parameter, but does not provide deeper semantics for other 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 installs Helm charts and mentions two modes (standard and template-based). It is specific enough to distinguish from the sibling 'upgrade_helm_chart'.

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 guidance on when to use this tool versus alternatives like 'upgrade_helm_chart' or when to choose template mode over standard. The agent must infer usage from context.

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