Step into

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

Annotations already indicate readOnly=false and destructive=false. The description adds that the tool advances into the current call and returns a new pause snapshot, which is useful behavioral context. However, it does not disclose preconditions, side effects on execution state, or potential blocking behavior when the target is not paused.

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?

A single sentence with no filler: "Step into the current call and return the new pause snapshot." The core action is front-loaded and every word adds meaning.

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?

The description covers the core action and the returned pause snapshot, and sessionId is adequately documented in the schema. However, with no output schema and no description of timeoutMs behavior or the requirement to be in a paused state, the definition is not fully complete for reliable invocation in all cases.

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 description coverage is 50%: sessionId is documented in the schema, but timeoutMs is not. The description does not explain the timeoutMs parameter or clarify when sessionId is required, so it fails to compensate for the missing schema documentation.

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 uses a specific verb and resource: "Step into the current call," and specifies the result: "return the new pause snapshot." This clearly conveys what the tool does and differentiates it from siblings like debug_step_over and debug_step_out based on the stepping semantics.

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 given about when to prefer debug_step_into over debug_step_over or debug_step_out, and no exclusions or alternative suggestions are mentioned. The intended usage is only implied by the tool name and the phrase "step into," leaving the agent to infer the decision context.

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