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. It mentions 'timeout' but fails to explain what happens when the timeout expires (exception, null return, empty object) or what constitutes an 'event' in this debugging context. The blocking nature is implied but not explicit.

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 brief (5 words) with no redundant language. However, it may be excessively terse given the 0% schema coverage and lack of annotations, verging on under-specification 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?

Given this is a debugging synchronization primitive with no output schema and no annotations, the description omits critical context: event types handled, timeout failure behavior, return value structure, and thread-safety implications.

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 0%, requiring the description to compensate. It references 'timeout' which maps to the timeout_ms parameter, but does not clarify the unit (milliseconds), the default value (30000), or whether 0 means infinite wait. Baseline compensation is partial.

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 provides a clear verb ('Wait') and target ('next event'), and implicitly distinguishes from sibling debug.get_last_event by emphasizing the blocking/waiting nature. However, it lacks explicit differentiation regarding when to prefer this over polling alternatives.

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 debug.get_last_event or event breakpoints. It does not mention prerequisites (e.g., being attached to a VM) or typical usage patterns.

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