mcp-netcoredbg

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

With no annotations provided, the description carries full burden. It states it starts debugging but omits behavioral details: whether it spawns a new OS process, whether it blocks until termination, what happens if symbols are missing, or that it establishes a persistent debug session (implied by sessionId parameter but not confirmed).

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?

Two sentences with zero waste. First establishes purpose, second adds the debug symbols constraint. Appropriately compact given the rich, self-documenting schema.

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?

Adequate for initiation but minimal given complexity. No output schema exists, yet description doesn't clarify the resulting debug session state (paused vs running) or side effects (process creation). Covers the essential pre-condition (debug symbols).

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 crucial semantic constraint that the DLL must be 'built with debug symbols'—critical information for successful debugging not present in the schema's generic 'Path to the .NET DLL to debug'.

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?

Clear verb ('Start debugging') and resource ('.NET application'), and specifies the DLL requirement. However, it does not distinguish from sibling 'attach' (connect to existing process) or 'launch_watch' (file watching), which is important given the debug context.

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 'launch' versus 'attach' (which connects to an already-running process) or other initiation methods. No mention of prerequisites like requiring a debuggable build configuration.

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