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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds real value beyond that by saying checkpoints are 'immutable' and belong to a 'shared Studio draft,' but it omits what happens when the sequence is out of range and whether recovery has side effects on the current draft.

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 or redundancy. It is well structured but undersized relative to what the agent must know, so brevity costs information rather than being purely efficient.

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?

An output schema exists, so return values needn't be explained, but for a two-parameter tool with 0% schema coverage the description should clarify what sequence means and how checkpoints relate to the live draft. As written, the agent knows the broad purpose but not how to select a checkpoint 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 0%, so the description carries the full burden for two required parameters and explains neither. It never says that draft_id identifies the shared Studio draft or that sequence selects the checkpoint index (the schema only bounds it 0-64 without meaning), leaving the agent to guess the semantics of the primary selection 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?

The description names a specific verb and resource: 'Recover an immutable earlier checkpoint of a shared Studio draft.' An agent can distinguish this from get_design_draft (current draft state) because 'earlier checkpoint' is explicit, but it never names the sibling it contrasts with, so the differentiation is inferred rather than stated.

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?

'Earlier checkpoint' implies the recovery use case, which gives some signal about when to reach for this tool over the current-draft tools. There is no explicit when-to-use, when-not-to-use, or named alternative, and nothing says whether checkpoints must already exist or how far back 0-64 reaches.

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