unity_packages_info

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

With no annotations, the description bears full responsibility. It indicates a read-only operation ('Get'), but does not disclose behavior beyond that, such as error handling, prerequisites (package must be installed), or impact on system state. The port parameter description provides some context for routing but not tool behavior.

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 of 10 words, highly concise and front-loaded with the core purpose. Every word is meaningful, with no redundancy or unnecessary detail.

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 adequately conveys the tool's function for a simple info-retrieval task, but it lacks details about output format (e.g., JSON structure, fields beyond versions/dependencies) and does not address edge cases like package not found. For a tool with no output schema, this leaves some gaps in understanding.

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. Parameter descriptions add value: 'name' includes an example, and 'port' explains its purpose and when to use it ('Get this from unity_select_instance' and 'ALWAYS include this parameter' for multiple instances). This exceeds the baseline by providing actionable guidance beyond the schema.

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 'Get detailed info about an installed package including versions and dependencies,' specifying the action (Get) and resource (detailed info about a specific installed package). It distinguishes from siblings like unity_packages_list (list packages) and unity_packages_search (search packages) by targeting a single package's details.

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 retrieving details of a specific installed package, but it lacks explicit guidance on when to use this tool versus alternatives. No when-not conditions or direct reference to siblings are provided.

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