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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description usefully adds that checkpoints persist in shared version history and the exported preset. However, it never says whether action=delete irreversibly drops a checkpoint or what happens to untracked edits, which is the key risk for a destructive-annotated 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?

Three short sentences, front-loaded with the primary action before the secondary management modes. Zero filler, though the phrase 'with a short description' is slightly loose relative to the 'label' param.

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?

For a 6-parameter mutation tool with no output schema and 0% schema description coverage, the description covers the semantics of the create/rename/delete flow but leaves the required sessionId, token, and baseRevision unexplained. An agent could call it, but might supply an arbitrary baseRevision without understanding its role.

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 coverage is 0%, so the description must carry parameter meaning; it explains label (short description), the action enum values, and checkpointId for managing existing versions. It says nothing about sessionId, token, or especially the required baseRevision (likely concurrency control), leaving three of six parameters undocumented.

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 and resource: 'Create a restorable version of the current shared preset' with a clear scope (shared preset, version history). It also discloses the secondary modes (rename/delete via action), so the agent understands the tool is not purely a create. It does not explicitly name restore_session as the counterpart, which keeps it from a 5.

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?

'Also use before a substantial experiment' gives an explicit trigger condition, and the closing sentence tells the agent to route rename/delete management through action + checkpointId rather than another tool. No when-not guidance or named alternative for the restore side, but the usage context is clear.

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