unity_hub_available_releases

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

No annotations are provided, so the description carries the burden. It states the tool lists available versions, implying a read-only, non-destructive operation. However, it does not disclose behavior like pagination, caching, or network dependency. The simplicity of the tool (no parameters) reduces the need for extensive disclosure.

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 sentence that is concise and front-loaded with the action. Every word is necessary.

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 tool has no parameters and no output schema, the description adequately explains its purpose. However, it could mention that results may be filtered or updated from Unity's servers. Still, for a simple list tool, it is complete enough.

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 input schema has no parameters, and schema description coverage is 100% (no params to document). The description adds value by clarifying what is listed (versions for download), beyond the schema's empty properties. Baseline for 0 params is 4.

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 lists Unity Editor versions available for download from Unity Hub. The verb 'List' and resource 'Unity Editor versions' are specific. It distinguishes from siblings like unity_hub_install_editor (which installs) and unity_hub_list_editors (which likely lists installed 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 implies usage for checking available downloads, but no explicit when-to-use or alternatives are given. However, the context of sibling tools (e.g., unity_hub_list_editors for installed editors) provides implicit differentiation. No guidance on prerequisites or restrictions.

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