session-revert

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

With no annotations provided, the description must disclose behavioral traits itself. It only mentions the default label behavior and that it is an undo step, but fails to mention potential side effects (e.g., permanent loss of changes since the checkpoint), required prerequisites (e.g., existence of a checkpoint), or failure behavior. This is insufficient transparency for a mutation 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?

The description is a single concise sentence that is front-loaded with the core action, followed by a parenthetical for the default and a summary of behavior. Every word adds value, with no fluff or repetition.

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?

The tool is simple with two optional parameters and no output schema. The description gives the essential function and default behavior, but lacks context on prerequisites (e.g., needing a checkpoint), failure cases, and whether it affects only the specified object or the active one. Adequate for basic use, but not fully complete given the lack of annotations and schema descriptions.

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?

The schema description coverage is 0%, so the description must compensate. It explains the 'label' parameter's default ('most recent if no label') but does not explain the 'object' parameter's default (which the schema title says is 'active'). It also does not clarify what

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 uses a specific verb 'Restore' with a clear resource 'object from a checkpoint', and it also mentions default behavior ('most recent if no label') and that it acts as 'one undo step'. This clearly distinguishes it from siblings like session-checkpoint (which creates checkpoints) and app-undo (which undoes the last action).

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?

The description gives no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor any sibling tools like session-checkpoint or app-undo. The phrase 'one undo step' hints at a relationship to undo, but there is no clear context or direction for selection.

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