Get HelmRelease details

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

Beyond the readOnly/idempotent annotations, the description discloses that `chart_source_url` is normalized rather than pullable, that chartRef/OCIRepository releases have real chart info in `source_urls`, and that `resolved_chart` surfaces the true name. It also explains the pagination and view behaviors.

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 structured with bullets, front-loaded with the core purpose, and each sentence adds value (view explanations, caveats, and cross-reference). It is long but earned.

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 a rich schema (8 params, enums, defaults) and output schema present, the description covers the tool's complexity thoroughly: it explains all three views, the data nuances, and provides a workflow. Gaps like error handling are not needed given the structured data.

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?

Although the schema already documents all 8 parameters (100% coverage), the description adds interpretive guidance—e.g., how `value_paths` from summary settings work as-is including array forms, and how `view` controls which parameters apply. It also gives a concrete id example. This exceeds baseline 3.

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 states 'Get details for one chart by its kubesearch.dev release id' with a clear verb and resource. It distinguishes from sibling tools by referencing `kubesearch_search_releases` for the id and describing three specific views (summary, deployments, values) that are unique to this tool.

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 explicitly says 'Start here' for summary view, tells users to use deployments to find a repo to drill into, and describes values as the drill-down. It also directs users to `repo_clone` for confirmation, providing alternative navigation.

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