gdb_next

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

Without annotations, the description carries the burden. It discloses that the tool steps over functions and requires a paused state. However, it does not mention potential side effects, timeout behavior, or what happens if the program is not paused. The timeout_sec parameter is in the schema but not described behaviorally.

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 three concise sentences with no wasted words. The crucial condition is highlighted in all caps. Front-loaded with the core action.

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 step-over tool with no output schema, the description sufficiently covers the purpose, prerequisite, and usage condition. It could mention that the tool resumes execution and then pauses again, but this is implicitly understood.

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?

Schema coverage is 100%, so baseline is 3. The description adds context that session_id comes from gdb_start_session, which is helpful but minimal beyond what the schema already says.

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 the action: 'Step over to the next line (doesn't enter function calls).' This clearly distinguishes it from gdb_step (which steps into functions), providing a specific verb and resource.

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 provides clear usage context: 'Only works when program is PAUSED at a specific location' and 'Requires session_id parameter (obtained from gdb_start_session).' It implicitly contrasts with stepping into functions, but does not explicitly name the alternative sibling (gdb_step).

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