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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the operationally critical specifics the annotations cannot convey: the deletion scope (everything since the chosen checkpoint), irreversibility, and the immediate public-facing side effect when the live version is among the deleted checkpoints. This is exactly the extra context an agent needs before invoking a destructive 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?

Four short sentences, front-loaded with the destructive consequence and the resulting state before the public-blog caveat. Every sentence carries information an agent needs; only minor loss from the mid-sentence line wrapping rather than tighter prose.

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?

Safety is covered by annotations, return shape is covered by the output schema, and the description adds the destructive/irreversibility and live-site impact facts. The remaining gap is procedural: how to discover a valid CheckpointID and whether the design must be inactive first, which would make it fully self-sufficient.

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?

There is one parameter with full schema coverage (UUID format and pattern documented in the schema itself). The description adds no meaning beyond that — it never says the ID must be an existing checkpoint for this design or how to obtain it — so the baseline of 3 applies.

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: restoring a blog design to a chosen checkpoint, with the resulting state made explicit ('Selected checkpoint becomes the current one'). It does not explicitly contrast with nearby siblings like blog_design_activate or blog_design_save, but the semantics are distinct enough that an agent can select it without opening the schema.

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?

Usage is implied through consequence ('deletes all checkpoints created since the chosen one'), which tells the agent this is a rollback rather than a browse operation. However, it never states prerequisites or where the CheckpointID comes from (e.g., blog_design_checkpoint_list), nor does it name an alternative when the agent merely wants to inspect checkpoints.

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