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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds genuinely non-obvious behavior beyond them: restoring also sends the version to connected destinations, an external side effect. It does not say whether the current chart state is replaced or recoverable, which matters for a write tool.

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 front-loaded sentence with no filler, and the side effect is stated up front rather than buried. Its brevity is efficient but leaves no room for the parameter or state-change detail an agent needs.

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 two undocumented required parameters and no output schema, the definition should explain what gets identified, what happens to the existing chart content, and what the send-to-destinations step implies. None of that is present, so an agent cannot call it confidently without opening the schema.

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 both required parameters, so the description must carry their meaning and does not: it never says whether 'id' is a chart id or version id, nor what 'version' numbering refers to. The phrase 'a saved version' only loosely gestures at the version parameter.

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?

Specific verb ('Restore') plus resource ('a saved version'), with the additional consequence that the restored version is pushed to connected destinations. It is clearly distinct from the generate_* and list_chart_versions siblings, though it never names an alternative.

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?

No statement of when to use this versus list_chart_versions, update_living_chart, or schedule_chart, and no prerequisites (e.g. that the version must already exist or that destinations must be configured). Usage is only inferable from the verb.

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