helm_lint

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

With no annotations, the description carries the behavioral burden. 'Lint and validate' conveys a non-destructive checking operation and the phrase 'for errors and best practices' adds scope. It does not, however, state whether Pro/api_key entitlements are required or describe the returned result, leaving some behavior implicit.

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, front-loaded sentence contains the verb, resource, and objective with no filler. Every part earns its place, though '(Pro)' would benefit from a short explanation in a fuller definition.

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?

For a one-action, three-parameter tool with a fully covered schema, the description is nearly sufficient. Missing context is the output/return format and the meaning/entitlement of '(Pro)' and api_key, and there is no output schema to fill that gap.

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% — chart_name, strict, and api_key are each described in the schema. The description adds no parameter-level details, so it stays at the baseline without compensating beyond the schema.

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 uses the specific verb phrase 'Lint and validate' and names the resource, 'a Helm chart,' with explicit outcomes: 'errors and best practices.' This clearly distinguishes helm_lint from siblings like helm_generate_chart, though it does not call out any sibling by name.

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 intended usage is implied by the verb: use this tool when a Helm chart needs linting/validation. However, the description gives no explicit when/when-not guidance or alternatives, and the '(Pro)' marker is not explained in terms of who should or shouldn't call it.

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