DebugStepIn

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the mutation/non-repeatable profile is covered. The description adds genuinely useful context by noting it does not block the MCP HTTP server, but it does not say whether the step completes asynchronously, whether WaitForPause is required afterward, or what 'Command execution result' actually contains.

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?

Front-loaded with the core action and kept to two short lines with no filler. The trailing 'Returns: Command execution result' is vague boilerplate, but it costs little.

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 state-mutating debugger control with no output schema, the definition covers the action and the non-blocking trait but omits execution prerequisites (must be paused), behavior on non-call instructions, and any indication of what the result means. Adequate but with clear gaps.

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 tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to disambiguate beyond what the empty schema already conveys.

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?

States a specific verb ('step into') and object ('the next instruction'), which is clear on its own. However, it never explicitly distinguishes itself from DebugStepOver, DebugStepOut, or DebugRun, leaving the agent to infer the difference between 'into' and 'over' from naming convention alone.

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 when-to-use guidance and no alternatives named, despite five closely-related stepping/run siblings. It also omits the essential prerequisite that the debuggee must already be paused; nothing tells the agent when stepping is valid vs. when to call DebugRun or WaitForPause first.

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