reverse-next

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

Discloses blocking behavior, session requirement, and the distinction between stepping by source line vs instruction. Although no annotations exist, the description adds sufficient behavioral context.

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?

Compact and well-organized: begins with core functionality, then requirements and alternatives. Every sentence adds value with no redundancy.

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?

Fully covers tool purpose, prerequisites, parameter behavior, and relationship to sibling tools. Output schema exists, so omission of return values is acceptable.

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?

Explains count and instruction parameters with defaults and behavior. session_id is not described but its purpose is obvious from context. Since schema coverage is 0%, description compensates well.

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 steps backwards over previous source line or machine instruction. It distinguishes from reverse-step (which enters calls) and next (forward counterpart).

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?

Explicitly states requirement for rr replay session created with start_replay_session. Mentions when to use reverse-step instead, providing clear guidance on alternatives.

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