jdwp-mcp

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

No annotations provided, so description carries full burden. Fails to disclose critical debugging behavior: whether method execution has side effects in target VM, exception handling behavior, return value format, or thread safety implications. Only provides arg syntax examples.

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?

Two efficient sentences with no fluff. Front-loaded with purpose, followed by helpful (if compact) usage examples. Appropriate length for the complexity.

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 4-param debugging tool with mutation potential. Missing: relationship to sibling tools (how to obtain object_id), output format (no output_schema), execution safety warnings, and error conditions. Only 1 required param but no explanation of optional params' impact.

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 coverage is 75% (method param undocumented). Description adds syntax examples for args parameter ('list.get(0), map.get("key")'), clarifying expected arg format beyond schema's generic '[0], ["key"]' example. However, adds nothing for object_id, method, or thread_id 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 specific action 'Invoke a method on an object' with clear verb and resource. Distinguishes from sibling debug tools like debug.set_value or debug.inspect by specifying method invocation rather than field access or inspection.

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?

No guidance on when to use versus alternatives (e.g., debug.set_value for fields), no prerequisites mentioned (e.g., requiring active debug session or object_id from debug.get_variable), and no warnings about side effects or exceptions.

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