instantiate_prefab

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Instantiate' implies a mutating operation, but the description does not state whether it modifies the current scene, whether it is undoable, what happens if the prefab_path is invalid, or what the return value/output represents. This is a significant transparency gap.

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, efficient sentence with no filler. It is front-loaded with the core action. However, it is so brief that it underspecifies the tool's behavior, so it loses one point for being under-developed rather than merely 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?

At 0% parameter coverage, no annotations, and a one-line description, an agent has too little information to invoke this tool correctly. There is no guidance on coordinate systems, parent relationships, or level-loading requirements. The description is minimally viable for purpose but not for correct usage.

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 0%, and the description does not explain any of the three parameters. prefab_path, position, and parent_id have no added meaning beyond their raw schema definitions. With such low coverage, the description was expected to compensate and does not.

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 states a clear verb ('instantiate') and resource ('prefab') with a scoping qualifier ('in the current level'). It is easy to understand what the tool does. However, it does not explicitly differentiate itself from sibling tools like create_entity or create_prefab_from_entity, so it does not fully earn a 5.

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 provides no guidance on when to use this tool versus alternatives such as create_entity, duplicate_entity, or create_prefab_from_entity. It also does not mention any prerequisites like needing a level loaded or how it differs from related creation tools.

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