jdwp-mcp

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 it specifies the scope affects 'all threads' (distinguishing from single-thread operations), it lacks critical context: whether this blocks until the next breakpoint, what happens if threads are already running, or any error conditions.

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?

At three words, the description is maximally concise and front-loaded. Every word earns its place with no redundancy or structural issues.

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 zero-parameter debugging command with no output schema, the description covers the minimum viable semantics. However, given the lack of annotations, it should disclose behavioral aspects like asynchronous versus blocking execution or state requirements to be fully complete.

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 tool accepts zero parameters (empty schema), which according to the rubric establishes a baseline of 4. The description correctly implies no configuration is needed, matching the schema.

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 the specific verb 'Resume' with the resource 'threads', clearly indicating it continues execution. It implicitly distinguishes from the sibling 'debug.pause' and step commands, though it could explicitly mention 'execution' or 'program' for absolute clarity.

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 step_into/step_over, nor does it mention prerequisites (e.g., that the program should be paused first). No alternatives or exclusions are mentioned.

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