jdwp-mcp

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

No annotations provided, so description carries full behavioral burden. Fails to disclose what constitutes an event, whether retrieval is destructive (clears buffer), error handling when no events exist, or expected response format.

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?

Extremely efficient three-word sentence with zero redundancy. Front-loaded with the action and target, appropriate for a simple getter tool.

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?

Minimally adequate for a parameterless tool but lacks critical context given no output schema or annotations: missing event structure details, distinction from debug.wait_for_event, and lifecycle of the 'last' event buffer.

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?

Zero parameters present; meets baseline expectation. Description implicitly confirms no filtering by not mentioning parameters, which is acceptable given the empty 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?

Clear verb and resource ('Show last breakpoint/step event'), identifying it retrieves recent debugging events. Lacks explicit distinction from siblings like debug.wait_for_event or debug.trace_result, and 'Show' is less precise than 'Retrieve'.

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?

Provides no guidance on when to use versus alternatives (e.g., debug.wait_for_event which blocks for new events vs. this which retrieves history). No mention of prerequisites like active debugging session or connected VM.

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