debug_step_over

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

Adds that it returns the new stop location, but does not disclose that stepping over mutates execution state. Annotations are neutral, so description could better cover side effects.

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?

Two efficient sentences with no waste. Front-loaded with action and result.

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, description states purpose and return. However, return value 'the new stop location' is vague without output schema; could specify structure or examples.

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?

Input schema covers the only parameter with a description, so description adds no extra meaning. Baseline 3 applies due to 100% schema coverage.

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?

Description clearly states 'Step over one line in the paused game' with a specific verb and resource. It distinguishes from sibling tools like debug_continue or debug_pause by focusing on line-by-line stepping.

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?

Implies usage when game is paused, but does not explicitly state when not to use it or provide alternatives among sibling tools like debug_continue.

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