javalens-mcp

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

No annotations are provided, so the description carries full burden. It discloses key behavioral traits: it's a prerequisite operation, loading may take time ('may take a few seconds for large projects'), and it supports specific project types (Maven, Gradle, plain Java). However, it doesn't mention error handling, memory implications, or whether the load is persistent across sessions.

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 well-structured with clear sections (DESCRIPTION, USAGE, OUTPUT, Supports, WORKFLOW), front-loading key information. Every sentence adds value, such as prerequisites, output details, and workflow steps. It could be slightly more concise by integrating some details, but it's efficient overall.

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 1 parameter with 100% schema coverage and no output schema, the description is mostly complete. It explains the tool's role in the context of sibling tools, outlines output ('Project structure summary'), and provides a workflow. However, without annotations or output schema, it could benefit from more details on error cases or exact output format.

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 description coverage is 100%, so the baseline is 3. The description adds value by specifying the parameter usage in the USAGE section ('load_project(projectPath="/path/to/project")'), clarifying it requires an 'absolute path,' and listing supported project types that help interpret the path. It doesn't provide format details beyond the schema's 'Absolute path to the project root directory.'

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 clearly states the tool's purpose: 'Load a Java project for analysis.' It specifies the verb ('Load'), resource ('Java project'), and purpose ('for analysis'). It distinguishes from siblings by explaining this is a prerequisite for other analysis tools, unlike tools like 'analyze_file' or 'search_symbols' that perform specific analyses after loading.

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 explicit usage guidelines: 'MUST be called before using other analysis tools.' It names a specific alternative ('health_check') to verify loading and lists other tools ('search_symbols, find_references, etc.') as follow-ups. The workflow section details when to use it in sequence with other tools.

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