jdwp-mcp

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

No annotations provided, so description carries full burden. States 'Search' implying read-only, but lacks critical details: return format (class names? objects? count?), search semantics (substring? regex? case-sensitive?), and performance characteristics for large JVMs.

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 5 words with front-loaded action. No redundancy, though brevity leaves behavioral gaps given lack of annotations and output schema.

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?

No output schema and no annotations present. For a debugging search tool, description should specify return value structure and search behavior (wildcards, case sensitivity) but fails to compensate for missing structured metadata.

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 has 100% coverage with helpful examples (UserService, com.example.User). Description adds minimal context ('name pattern'), meeting baseline expectations when schema documentation is comprehensive.

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 'Search' with resource 'loaded classes' and scope 'by name pattern'. Implicitly distinguishes from 'wait_for_class' by emphasizing currently loaded classes, though explicit sibling differentiation is absent.

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 versus sibling tools like 'wait_for_class' (which waits for future loads) or 'inspect' (which examines instances). No mention of prerequisites or search strategy.

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