step_over

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

Describes blocking behavior, state requirement, effect of not entering functions, and return of new location. With minimal annotations (only openWorldHint=false), this adds significant behavioral insight, though it doesn't cover potential side effects like variable changes.

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 well-organized: action, requirement, behavior, important note, escape hatch. Every sentence adds value without 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?

Covers core stepping behavior, state requirement, and return info. Lacks explanation of thread_id parameter, but given optional nature and presence of sibling step tools, it is largely complete for its purpose.

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 single parameter thread_id is not mentioned in the description (0% schema coverage). While its purpose may be inferred, the description does not clarify its role or default behavior, leaving ambiguity for the agent.

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 explicitly states 'Step over to the next line' and 'Executes the current line without entering function calls', clearly defining the action and distinguishing it from step_into and step_out among siblings.

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?

Prerequisite 'State: STOPPED required' is given, and the post-action instruction to inspect variables provides usage context. However, it does not explicitly compare with step_into/step_out or mention when not to use.

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