create_prefab_from_entity

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly states the primary side effect (writing a file to disk), a key constraint (path relative to project root), and an important non-effect (the level is not modified). It does not mention whether an existing file at the path is overwritten, but the disclosed behavior is otherwise solid and honest.

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 two sentences with no wasted words. The primary action is front-loaded, and the two most important operational details—relative path and non-modification of the level—are placed immediately after. Every sentence earns its place.

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?

This is a low-complexity tool with two simple string parameters and an output schema present, so return-value documentation is not needed. The description covers what the tool does, how to interpret the path, and the recommended next step. It is slightly incomplete regarding overwrite behavior, but it is otherwise sufficient for an agent to invoke the tool correctly.

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?

The input schema provides only parameter names and types with 0% coverage in descriptions, so the description must compensate. It adds meaningful semantics for both parameters: entity_id is the existing source entity, and prefab_path is a path relative to the project root. It could add more detail such as expected file extension, but the core meaning of both parameters is clarified.

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 specific action—'Write a prefab file to disk from an existing entity'—with a clear resource (prefab file) and source (existing entity). It also distinguishes the operation from related tools by noting that the level is not modified, which separates it from save_prefab and similar workflow steps.

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 clear operational context: the path is relative to the project root, and the tool does not modify the level. It also gives a direct follow-up instruction—'use instantiate_prefab afterwards to place the saved prefab'—which tells the agent what to do next. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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