unity_hub_set_install_path

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

The description indicates a write operation (setting a path), which is consistent with the tool's purpose. No annotations are provided, so the description must convey behavioral traits. It does not mention side effects (e.g., does it affect existing installations?) or error conditions (e.g., invalid path). Adequate but not detailed.

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?

Single sentence, no wasted words. Clearly states the purpose without redundancy.

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 tool (1 param, no output schema), the description is mostly complete. It could mention if the path must exist or be writable, but overall it provides sufficient context for a basic setter tool.

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%, and the description does not add extra meaning beyond the parameter name 'path'. The description's mention of 'installation directory' aligns with the schema, but no additional details on path format (absolute vs relative, OS-specific constraints). Baseline 3 is appropriate.

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 ('Set') and the resource ('default installation directory for Unity Editors'). It distinguishes from sibling tools like unity_hub_get_install_path and unity_hub_install_editor, though it could be more specific about what 'default' means.

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?

No explicit guidance on when to use this tool versus alternatives like unity_hub_install_editor or unity_hub_get_install_path. Context implies it's for changing a global setting, but no exclusions or prerequisites are mentioned.

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