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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the safety profile is covered. The description adds real value beyond them: the reconciliation re-application behavior and the recovery path ('Not reversible except by rolling forward again'), which tells the agent the blast radius and how to undo.

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 action and its scope are front-loaded, and the snippet is short. The CLI-twin aside ('the twin of ankra cluster roll-to') is slightly ornamental but helps cross-referencing; no sentence is wasted.

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?

There is no output schema, so the description must carry the framing, and it does: what changes (all stacks), what triggers re-application (reconcile), prerequisite source (get_stack_history), and reversibility. Only a note on expected timing/return behavior is missing.

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 all three parameters (cluster_id, version_id, cluster_name) are already documented, including version_id's origin in get_stack_history. The description repeats that provenance but adds no syntax, format, or selection 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 ('roll ... back to an earlier resource version') and resource ('a cluster's whole definition'), plus the scope qualifier 'whole definition' and the CLI twin 'ankra cluster roll-to'. An agent can immediately separate it from sibling mutations like rollback_addon or reconcile_cluster.

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?

Names the alternative explicitly ('rollback_addon rolls one addon') with the distinguishing criterion (whole cluster vs single addon), and tells the agent where the input comes from ('Take the version id from get_stack_history'). It lacks an explicit when-not-to-use or prerequisite check, so it stops short of a 5.

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