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

readOnlyHint=true already declares the safety profile, and the description reinforces it ("Read-only") while adding genuine non-obvious context: registry credentials are never returned, so an agent won't hunt for secrets. It does not disclose pagination behavior, but for a simple read tool that is a minor gap.

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 resource and returned fields, then usage and the sibling pointer. Dense but every clause carries information; the CLI-twin parenthetical is slightly meta but helps an agent familiar with that CLI.

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 takes on the burden of describing return shape (name, URL, kind, credential name, sync state, chart counts) and does so. Combined with the credential-redaction note and usage guidance, an agent has everything needed to call it correctly.

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% and each of the three params (page, search, page_size) is documented in the schema. The description adds nothing about parameters, so baseline 3 is appropriate when the schema does the work.

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 resource (the organisation's connected Helm chart registries) and enumerates the returned fields (name, URL, kind, credential name, sync state, chart counts). It also explicitly names its sibling add_helm_registry, so an agent can distinguish list from create without opening either schema.

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?

Gives concrete when-to-use cases ("answer where a chart comes from or whether a private registry is connected") and the contrasting alternative (add_helm_registry connects a new one). Nothing about tool selection is left to inference.

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