mcp-netcoredbg

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

With no annotations provided, the description explains the core navigation action (entering the function call). However, it omits important behavioral details: that execution advances and pauses at the first line of the callee, what happens if no function call exists on the current line, and whether this modifies program state.

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?

Extremely concise single sentence of seven words with zero redundancy. Front-loaded with the action verb. The brevity is appropriate for standard debugger commands, though the absolute minimalism contributes to missing contextual prerequisites.

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?

Lacking annotations and output schema, the description covers the basic debugger action but misses important context: execution state requirements (must be paused), relationship to other step commands in the sibling list, and error behavior. Adequate but clearly incomplete for a control-flow tool.

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% for both threadId and sessionId. The description adds no parameter-specific guidance (e.g., when to explicitly specify sessionId versus accepting the default), meeting the baseline expectation when the schema already documents fields adequately.

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?

Uses specific debugger terminology ('step into') combined with target resource ('function call on the current line'), clearly indicating it enters the callee rather than stepping over or out. Implicitly distinguishes from siblings step_out and step_over through standard semantics, though it could explicitly clarify this is a debugger execution control action.

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?

Provides no guidance on when to use versus alternatives like step_over or step_out. Critically omits prerequisites such as requiring the debugger to be in a paused state before invocation, which is essential for correct usage among the sibling debugging tools.

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