unity_hub_install_modules

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 does not mention whether the operation is destructive, requires network access, can be undone, or any side effects, leaving significant gaps for an install action.

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 a single, focused sentence with no extraneous words, effectively front-loading the core action and context.

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 simple 2-parameter input and no output schema, the description is minimally adequate. However, it lacks details on error handling, specific platform module options, or verification steps, which would be beneficial for a complete context.

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 coverage is 100% so baseline is 3. The description adds slight value by including example module names (android, ios, webgl) beyond the schema's generic description, but does not provide new meaning for the version parameter.

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 verb 'Install' and the resource 'additional platform modules' to an already-installed Unity Editor version, which distinguishes it from sibling tools like unity_hub_install_editor or unity_hub_list_editors.

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 implicitly states the prerequisite that the editor must already be installed, but does not explicitly provide when-not-to-use guidance or contrast with alternative tools like unity_hub_install_editor for initial installation.

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