jdwp-mcp

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. It fails to clarify critical mutation behaviors: whether changes persist after continuing execution, type validation rules, thread safety, or error conditions (e.g., if the variable doesn't exist in the frame).

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?

Single sentence of seven words is appropriately front-loaded and free of redundancy. However, given the lack of annotations and output schema, the brevity leaves critical gaps rather than being optimally efficient.

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 state-mutation tool with no annotations, no output schema, and partially undocumented parameters, the description is insufficient. It omits expected context for debugger operations: target requirements, persistence semantics, and success/failure indicators.

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 50% (thread_id and value are described; frame_index and name are not). The description grammatically implies that 'name' is the variable name and 'frame_index' selects the stack frame via 'in a stack frame', but does not explicitly document the undocumented parameters or explain the default frame_index=0 behavior.

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 a specific verb ('Set') and identifies the resource ('local variable') and scope ('in a stack frame'). However, it does not distinguish from sibling tools like 'debug.eval' (which could also assign values) or clarify when to prefer this over other mutation methods.

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 guidance provided on when to use this tool versus alternatives, prerequisites (e.g., must be paused), or side effects. The description states what it does but offers no workflow context for the debugging scenario.

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