mcp-netcoredbg

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

No annotations provided, so description carries full behavioral burden. While it mentions breakpoint support, it omits critical execution details: return value handling, exception behavior, blocking vs async execution, process isolation, and side effect risks. For an arbitrary code execution tool, these omissions are significant.

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?

Three sentences with no redundant text. Front-loads the core action, follows with capability notes. Slightly too terse given the tool's complexity and safety implications—could accommodate one sentence on return behavior without sacrificing clarity.

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?

High complexity tool (8 parameters, arbitrary code execution, integration with rich debugging ecosystem) with no output schema and no annotations. Description fails to address the invocation lifecycle, session management (despite sessionId parameter), or how it integrates with sibling debugging workflow.

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%, establishing baseline 3. Description adds context for 'debug' parameter linking it to breakpoint capability, but does not elaborate on 'args' vs 'ctorArgs' distinction, 'sessionId' usage patterns, or expected formats beyond what schema already provides.

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-resource combination ('Invoke a specific method in a .NET assembly'). Mentions debug capability which contextualizes it within the debugging tool family. However, it does not explicitly distinguish from siblings like 'evaluate' (expression evaluation) or 'launch' (program startup).

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 conditional guidance for the debug parameter ('Use debug mode to set breakpoints'), but lacks explicit when-to-use/when-not-to-use relative to sibling execution tools. Does not clarify if this requires an active debug session or operates standalone despite the presence of 'sessionId' parameter.

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