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 of behavioral disclosure. While 'Get' implies read-only access, there is no mention of output format, performance characteristics, or whether this blocks execution. Minimal behavioral disclosure.

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 brief (5 words) with no redundant language. However, it is excessively terse to the point of under-specification rather than true conciseness. It is front-loaded but content-deficient.

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?

For a debugging tool with 3 optional parameters and no output schema, the description is inadequate. It fails to explain the relationship between threadId/sessionId and 'current', the format of returned stack frames, or how 'depth' truncation behaves.

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 all parameters (threadId, depth, sessionId) having descriptions. The description mentions 'current call stack' which loosely maps to thread/session concepts, but adds no syntax or semantic details beyond the schema definitions.

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 'Get the current call stack' is tautological, essentially restating the tool name 'stack_trace' as a verb phrase. It fails to distinguish from sibling inspection tools like 'scopes', 'variables', or 'threads' that also retrieve debugging state.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description does not indicate prerequisites (e.g., needing an active debugging session) or when to prefer this over 'threads' or 'scopes'.

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