mcp-netcoredbg

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it notes the output source (stdout/stderr), it fails to clarify critical behaviors: whether reading consumes/clears the buffer, whether the call blocks until output is available, or the format of returned data. 'Recent' implies temporal limits but doesn't define the buffer size or retention policy.

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, efficient sentence of six words. It is front-loaded with the verb 'Get' and contains no redundant or filler text. For a simple retrieval tool, this length is appropriate 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 tool's simplicity (2 parameters, 100% schema coverage, no output schema), the description is minimally adequate. It identifies the core resource (stdout/stderr) but could be improved by explicitly stating this reads from the target program's console output in a debug session, especially given the rich sibling tool context.

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 100%, with 'lines' and 'sessionId' fully documented in the schema (including the helpful cross-reference to list_sessions). The description field itself makes no mention of parameters, but given the complete schema coverage, it does not need to compensate. Baseline score applies.

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 clearly states the tool retrieves 'recent program output' and specifically identifies the source as 'stdout/stderr'. However, it does not explicitly contextualize that this applies to a debug session (implied only by the sessionId parameter schema), nor does it distinguish from the 'evaluate' sibling which might also return text output.

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?

The description provides no guidance on when to use this tool versus alternatives like 'evaluate' or 'variables'. It does not mention prerequisites (e.g., requiring an active session with a launched program) or whether this should be polled continuously versus called on-demand.

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