mcp-netcoredbg

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

With no annotations provided, the description carries the full burden. It discloses the destructive nature ('terminate') and specific mode being stopped ('hot reload'), but omits side effects, error conditions (e.g., if no watch is running), or state changes to the debug session.

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?

The description is a single, dense sentence with no filler words. Critical information ('hot reload', 'dotnet watch', 'terminate') is front-loaded and every word earns its place.

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?

Given the low complexity (one optional parameter, no output schema, simple action), the description adequately covers the tool's function. It could be improved by noting the default session behavior, but it is sufficiently complete for an agent to invoke correctly.

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 input schema has 100% description coverage for the optional sessionId parameter. The description adds no parameter-specific context, but given the high schema coverage, this meets the baseline expectation without penalty.

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 specific verbs ('Stop', 'terminate') with a specific resource ('dotnet watch process') and uniquely identifies the scope ('hot reload debugging mode'), clearly distinguishing it from generic terminate operations available in siblings.

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?

While the specificity of 'hot reload debugging mode' implies the context for use, there is no explicit guidance contrasting this tool with siblings like 'terminate' or 'terminate_session', nor does it state prerequisites (e.g., that launch_watch should have been called first).

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