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 but only indicates that threads are suspended. It omits crucial debugging context: whether this freezes the VM/program execution, if it's synchronous, whether it can be reversed via debug.continue, or behavior when called while already paused.

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 concise at only three words with no redundancy. Every word earns its place, though given the high complexity of the debugging domain with 25+ sibling tools, the brevity borders on insufficient rather than efficiently complete.

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?

Inadequate for a complex debugging tool ecosystem. With no output schema, no annotations, and high domain complexity, the three-word description fails to address expected behaviors, error conditions, or state requirements necessary for an AI agent to invoke this tool correctly.

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?

Input schema has zero parameters, which per evaluation guidelines establishes a baseline score of 4. The description appropriately reflects this by not mentioning any parameters.

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?

States a specific verb (Suspend) and target resource (all threads), which clearly identifies the tool's action. However, it could better distinguish from sibling stepping operations (step_into, step_over) by clarifying this halts execution entirely rather than advancing it.

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 this tool versus alternatives, nor any prerequisites. For a debugging tool with 25+ siblings, the description fails to indicate that this requires an active debug session (via debug.attach) or when to prefer this over breakpoints.

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