install_project

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state the underlying commands and the effect on the local Maven repository, which is useful. However, it does not mention side effects not captured elsewhere, such as test execution defaults, dependency building behavior, or overwriting existing local artifacts.

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 two sentences with no filler. The core action and target repository are stated first, and the multi-module capability is added in the second sentence. Every word contributes useful 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?

The description covers the main purpose, supported build tools, and multi-module capability, and the schema covers all parameters. Still, with no output schema and no annotations, it leaves some contextual gaps, such as what success/failure output looks like and how Java version selection is applied.

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 parameter schema already documents all 6 parameters. The description adds some context around multi-module support via the -pl flag, but it does not materially extend the meaning of the parameters beyond what the schema provides.

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 a specific action — install a Java project to the local Maven repository — and names the exact mechanisms (mvn install / publishToMavenLocal). This distinguishes it from sibling tools like build_project and compile_project, which do not install artifacts to a local repository.

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 gives clear context for when the tool is appropriate: when a Java project needs to be installed locally via Maven or Gradle. It also notes multi-module support, but it does not explicitly contrast the tool with siblings such as build_project or run_tests.

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