next

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

With no annotations available, the description must disclose behavioral traits. It only states 'Step over to next line' without describing side effects, state changes, or requirements (e.g., session must be paused). This is insufficient for an agent to understand the tool's behavior beyond the name.

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 extremely concise (5 words) but lacks structure or front-loading of key information. While it is short, it could benefit from a brief elaboration on context or prerequisites without becoming verbose.

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 low complexity (1 parameter, common debugger action), the description is minimal. It does not explain return values, preconditions (e.g., paused session), or how it interacts with breakpoints. Siblings like 'continue' and 'step' provide contrast but the description alone is insufficient for complete understanding.

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% and the 'sessionId' parameter description is clear. The tool description does not add any additional meaning beyond the schema, meeting the baseline expectation.

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 'Step over to next line' clearly indicates the tool performs a debugger step-over operation. It distinguishes from siblings like 'step' (step into) and 'stepout' (step out) by specifying 'over', though it could be more explicit about the action's effect on function calls.

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?

No guidance is provided on when to use this tool versus alternatives like 'step' or 'continue'. The description does not mention prerequisites (e.g., paused debug session) or exclusions.

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