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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds that this is the twin of a CLI command, but discloses no further behavior such as rate limits, caching, or error conditions. With annotations covering safety, a modest 3 is appropriate.

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 dense sentence front-loads the purpose, enumerates the returned fields, and ends with the read-only signal. No wasted words.

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 simple two-param read-only lookup with no output schema, the description conveys what the tool returns (description, maintainers, home, sources, versions, app version), which is the key missing structured info. It could go slightly further on sourcing the repository_url, but it is largely complete.

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 both parameters (chart_name, repository_url) are already documented, including the hint that the URL comes from list_available_charts or list_helm_registries. The description adds no syntax or format detail 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?

States a specific verb+resource ('Detailed information about a Helm chart') and enumerates what is returned (description, maintainers, home, sources, versions, app version). This clearly distinguishes it from siblings like get_chart_default_values, list_chart_versions, and render_chart_template.

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 implies this is for inspecting a known chart at a repository URL (dual of `ankra charts info`), but gives no explicit when-to-use versus alternatives like list_available_charts or get_chart_default_values. Usage is inferable but not stated.

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