unity_asset_instantiate_prefab

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

With no annotations, the description must disclose behavioral traits. It only states the action, omitting details like required permissions, potential side effects, return values, or that the prefab must exist. The port parameter hints at multi-instance handling but is not explained.

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, efficiently conveying the core action. However, for a tool with six parameters, it could be organized with more structure (e.g., brief parameter intent) without adding much length.

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 6 parameters, no output schema, and no annotations, the minimal description is severely incomplete. It does not explain prerequisites, return values, error conditions, or how parameters like position/rotation work.

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 67%, with some parameters (position, rotation) lacking schema descriptions. The tool description adds no parameter information beyond the schema, missing the chance to explain the nested objects or the purpose of port.

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 'Instantiate a prefab into the current scene' uses a specific verb (Instantiate) and resource (prefab) with destination (current scene), clearly distinguishing it from siblings like unity_gameobject_create or unity_asset_create_prefab.

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 gives no guidance on when to use this tool versus alternatives, such as when to instantiate vs create an empty GameObject, nor any exclusions or prerequisites.

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