jdwp-mcp

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

No annotations are provided, so the description carries full burden. It states the action (setting a default) but provides minimal behavioral context: it does not disclose whether the selection persists across calls, what happens if thread_id is invalid, whether this affects global debugger state, or if the change is validated immediately. For a stateful mutation tool, this is a significant gap.

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 extremely concise at five words with zero redundancy. Every word earns its place by conveying the core action and purpose. However, given the complete absence of annotations and the complexity of the debug tool ecosystem, it borders on underspecification rather than optimal conciseness.

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?

With only one well-documented parameter and no output schema, the minimal description is technically adequate to invoke the tool. However, given the tool is part of a complex 20+ tool debugging suite with stateful interactions, the description lacks necessary workflow context—specifically how this selection affects subsequent inspection operations and its relationship to debug.list_threads.

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% (thread_id is documented as 'hex e.g. 0x1a2b'), establishing a baseline of 3. The description adds no information about the parameter beyond what the schema provides, but the schema coverage is sufficient that no additional semantic clarification is strictly necessary.

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 resource ('thread') with clear scope ('default thread for inspection'). However, it does not explicitly differentiate from siblings like 'debug.list_threads' (which enumerates threads) or 'debug.attach' (which attaches to a process), though the verb 'select' implies a different action than 'list' or 'attach'.

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 phrase 'for inspection' implies usage context—use this when you want to inspect a specific thread—but lacks explicit workflow guidance. It does not mention prerequisites like obtaining thread_id from debug.list_threads, nor does it specify that subsequent inspection tools (debug.inspect, debug.get_stack) will target this selected thread.

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