unity_asset_instantiate_prefab

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

Annotations are not provided, so the description carries the full burden. It correctly implies a creation/mutation operation (instantiation), but does not disclose side effects (e.g., if the prefab is not found, or if the operation fails), nor the return value. It lacks details on whether it modifies the scene permanently or requires saving. The description is basic but not misleading.

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 conveys the core purpose. It is front-loaded and efficient, though it could be slightly expanded to include key details like 'Creates a new GameObject in the current scene from a prefab asset'. No wasted words.

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 complexity (6 parameters, nested objects, no output schema), the description is incomplete. It does not explain return behavior, error cases, or the effect on the scene. It also does not clarify the coordinate system for position/rotation. However, it covers the essential action. Annotations are absent, so the description should do more.

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 67%, with some parameters (prefabPath, name, parent, port) having descriptions in the schema. The description adds no additional meaning beyond the schema for those. Parameters like position and rotation are nested objects without descriptions, and the description does not clarify their format or behavior. The description does not compensate for the missing schema descriptions.

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 action ('Instantiate a prefab') and the target resource ('into the current scene'). It distinguishes from sibling tools like unity_asset_create_prefab (which creates a prefab from a GameObject) and unity_gameobject_create (which creates empty GameObjects). However, it could be more explicit about what instantiation entails (e.g., creating a runtime instance).

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 guidance on when to use this tool vs alternatives like unity_gameobject_create or unity_asset_create_prefab. It does not mention prerequisites (e.g., prefab must exist) or when not to use it. The 'port' parameter description gives a hint for multi-instance scenarios but no broader usage context.

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