unity_packages_info

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

No annotations provided, so description carries full burden. It states it gets info, but doesn't disclose side effects (none expected), permissions, or whether package must be installed. Also doesn't mention error cases or if package not found.

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 clearly stating purpose. Efficient, no fluff. Could be slightly more specific about what 'detailed info' includes, but overall concise.

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 no output schema and two simple params, description adequately covers the tool's purpose. However, lacks details on return format and error conditions, and no annotations to compensate.

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 description adds brief parameter context ('Package name, e.g. ...' and 'Target Unity instance port...'). However, it doesn't add much beyond what's in the schema; 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?

Description uses clear verb ('Get') and resource ('detailed info about an installed package including versions and dependencies'). It distinguishes from siblings like unity_packages_list and unity_packages_add by focusing on detailed info of a specific package.

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?

Implied usage when needing details about an installed package. No explicit guidance on when not to use or alternatives, but sibling names suggest other package tools exist. Context signal about port is provided in parameter description.

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