session_rollback

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

Without annotations, the description discloses destructive behavior (deletes steps) and the ability to continue. However, it lacks warnings about irreversibility, prerequisites, or side effects on assumptions or other session state.

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 concise: a clear purpose, a behavioral explanation, and parameter documentation. Every sentence adds value with no redundancy or fluff.

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 simple tool with one parameter and an existing output schema, the description covers the main functionality and edge case (0 clears all). Minor gaps: no mention of error handling for invalid step numbers or session state requirements.

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?

Despite 0% schema description coverage, the description fully documents the single parameter 'to_step': it explains 1-based numbering and that 0 clears all. This adds essential meaning 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?

The description clearly states the tool's purpose: rolling back to a specified step, keeping steps up to that step, deleting later steps. It distinguishes itself from sibling session tools by specifying the effect and allowing continued derivation.

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 implies usage when wanting to revert and diverge, but does not explicitly state when to use this tool over alternatives like session_abort or session_resume. No exclusions or conditions are provided.

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