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

The readOnlyHint=true annotation already tells the agent this is a safe read, so the description only needs to add context. It does add the "owned" qualifier, signaling an ownership requirement, but says nothing about ordering, pagination, or what a "saved version" contains.

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?

One short sentence with no filler and the resource front-loaded, so it is efficient. The efficiency comes at the cost of under-specification rather than deliberate brevity.

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 and no annotations beyond readOnly, the description should indicate what the returned versions look like (names, timestamps, ordering) and whether the list is paginated. It provides none of that, leaving the agent able to guess the action but not the result.

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 0% for the single required "id" parameter, so the description must carry the meaning. It only implies the id identifies a living chart the caller owns; it never states the id format, accepted values, or error behavior for non-owned ids.

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 specific verb ("list") and resource ("saved versions of a living chart"), which is enough to distinguish it from create/schedule/restore siblings. It stops short of naming the related restore_chart_version use case, but the core action is unambiguous.

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?

There is no statement of when to call this versus list_my_charts or restore_chart_version, and no prerequisite or exclusion is given. The only implied guidance is the "owned" qualifier, which hints at an access constraint rather than a usage decision.

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