unity_prefab_info

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

With no annotations provided, the description must disclose behavioral traits. It correctly states the tool is a read operation (get detailed prefab information) but does not mention side effects, authorization requirements, or rate limits. The description is accurate but not exhaustive.

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 concise at one sentence, but it is slightly dense and could be broken into two parts for clarity. It front-loads the key capabilities.

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's moderate complexity (4 parameters, no output schema), the description is reasonably complete. It explains the kind of information returned (overrides, variant status, components) and scope (assets and instances). However, no details about return format or errors are provided.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the tool's scope (prefab info) but does not provide additional detail about the parameters beyond what's in the schema. However, the 'port' parameter's description is very thorough and helpful for parallel-safe routing.

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 retrieves prefab information including overrides, variant status, and component changes. It explicitly mentions it works on both prefab assets and scene instances, which distinguishes it from sibling tools like unity_gameobject_info or unity_asset_list that cover different aspects.

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 prefab details but provides no explicit guidance on when to use this tool versus alternatives (e.g., unity_gameobject_info for general gameobject info, unity_component_get_properties for component details). It lacks any 'when not to use' or prerequisite information.

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