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

Beyond the readOnlyHint annotation, the description discloses that rendering happens server-side, requires no cluster connection, and installs nothing — meaningful side-effect information. It stops short of covering rate limits or the shape/format of the rendered result.

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?

Front-loaded with the core action and the read-only guarantee placed last, which is efficient. Minor redundancy in stacking two analogies ('like `helm template`' and 'the twin of `ankra charts template`') costs a little tightness.

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 implies the result is rendered Kubernetes manifests but doesn't state the return format (e.g., YAML text blocks) or whether multiple documents are returned. Otherwise it fully covers when and how to call the tool, including the 512 KiB values constraint inherited from the schema.

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 every parameter (including values_yaml, release_name, namespace defaults) is already documented. The description's mention of 'optional value overrides' only restates what the schema says, so the baseline 3 applies.

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 gives a precise verb+resource ('Render a chart version's Kubernetes manifests server-side') and anchors it with a familiar analogue ('like `helm template`'). It clearly distinguishes itself from installation-oriented siblings by stating 'no cluster connection, nothing is installed'.

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?

It names three concrete use cases: preview what an addon would deploy, verify that values produce the intended resources, and find image references before installing. The negative constraint ('nothing is installed') implicitly steers agents toward install/addon tools for actual deployment, though no sibling tool is named explicitly.

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