install_modpack

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

With no annotations provided, the description discloses several behavioral traits: the installation path, the default instance name, and the HMCL agent dependency with automatic startup. It goes beyond a minimal statement by revealing these operational details, though it does not cover edge cases like overwrites or permissions.

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 three sentences long and front-loaded with the main purpose. Each sentence adds necessary information: core action, input modes, and the HMCL requirement. There is no redundant or filler content.

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?

For a tool with 5 optional parameters and no output schema, the description covers the main usage scenarios, dependencies, and naming default. However, it omits the source parameter explanation and potential side effects. Given the tool's complexity, this is a solid but not exhaustive description.

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 schema has no descriptions for its 5 parameters, but the description explains path, id, versionId, and name, including the name default. The 'source' parameter is not addressed, leaving one parameter unclarified. Overall, the description compensates well for the lack of schema-level documentation.

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 what the tool does: installs a modpack as a game instance under a specific path. It distinguishes from siblings like download_modpack and install_hmcl by focusing on installation and mentioning both local file and remote download modes.

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 explains the two input modes (local path or id) and notes the HMCL agent requirement with auto-start. It provides clear context but does not explicitly state when to use this tool over alternatives such as download_modpack, so no exclusions are mentioned.

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