step

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

No annotations provided, so description carries full burden. Discloses key behaviors (enters called functions, machine instruction mode) but omits details like session state requirements, breakpoint interaction, or side effects during stepping. Adequate but not thorough.

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?

Very concise: two sentences for purpose and parameter explanation, with no extraneous text. Front-loaded with primary action, then parameter details, then alternative guidance.

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?

Given the tool's moderate complexity and presence of output schema, the description adequately covers behavior and parameters. Minor gap on 'session_id' but overall sufficient for AI agent to use correctly.

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?

Description explains 'count' and 'instruction' parameters with defaults and meaning, but does not mention 'session_id' which is required. With 0% schema coverage, the description should cover all parameters; missing one parameter reduces effectiveness.

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 it steps forward into the next source line or machine instruction and enters called functions. It distinguishes from sibling 'next' and mentions 'reverse-step' for RR sessions, making purpose unambiguous.

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 tells when to use this tool ('step into') vs alternatives: 'Use next to step over calls instead' and 'use reverse-step to step backwards' in RR sessions. Clear guidance on parameter usage with defaults.

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