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

Annotations already mark the operation as readOnlyHint=true, so the safety profile is covered. The description adds the 'post-install instructions' meaning and protocol support, but does not explain response behavior, error cases, or auth requirements. This is adequate but not especially rich beyond the annotations.

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 two concise sentences with no filler. It front-loads the core purpose and adds the relevant protocol detail in the second sentence, making it easy for an agent to parse quickly.

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 read-only fetch tool with an output schema, complete schema parameter coverage, and readOnlyHint annotation, the description is fully adequate. Nothing important is missing for an agent to select and invoke this tool 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 description coverage is 100%, so the schema already fully documents all three parameters. The description's protocol note adds a little extra meaning to repository_url, but it largely repeats schema content. Baseline 3 is appropriate because the description does not materially enhance parameter understanding.

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 a specific verb and resource: 'Get chart NOTES.txt (post-install instructions)'. It clearly distinguishes this tool from siblings like get_values and get_versions, which have different resources. The parenthetical also clarifies what NOTES.txt contains, leaving no ambiguity.

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 gives clear functional context: this tool is for retrieving post-install instructions as NOTES.txt, which implies when it should be used. It also states that it supports both HTTP/HTTPS repos and OCI registries, offering useful scope information. It does not explicitly name alternative tools or give when-not-to-use guidance, but the context is sufficient.

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