Java Decompiler MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that it 'Returns CFR status information' without explaining what that information includes, whether this is a read-only operation, if there are any side effects, or what format the response takes. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 with just two lines in Chinese. While concise, it's arguably under-specified rather than efficiently structured. The first line states the purpose, the second line indicates it returns something, but both lines could be more informative. It's not front-loaded with the most critical information.

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 the tool has zero parameters, 100% schema coverage, and an output schema exists, the description doesn't need to explain return values. However, for a status-checking tool among decompilation siblings, it should provide more context about what 'CFR status' means and why/when to check it. The description is minimally adequate but lacks helpful context about the tool's role in the ecosystem.

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?

The tool has zero parameters (schema coverage 100%), so there are no parameters needing semantic explanation. The description doesn't need to compensate for any parameter documentation gaps. The baseline for zero parameters is 4, as there's nothing to explain beyond what's already clear from the 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?

The description states '检查 CFR 反编译器状态' which translates to 'Check CFR decompiler status' - this provides a clear verb ('check') and resource ('CFR decompiler status'). However, it doesn't distinguish this tool from its siblings like 'get_java_version' or explain how this status check differs from decompilation operations. The purpose is understandable but lacks sibling differentiation.

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. There's no mention of when this status check is needed (e.g., before decompilation operations, for troubleshooting), nor does it differentiate from sibling tools like 'get_java_version' or the various decompile tools. The agent receives no usage context.

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