scene_set_spawn

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

The description discloses critical behavior beyond the annotations: it writes a new .gil in the workspace while leaving the official save untouched. It also explains coordinate semantics, camera behavior, and a concrete failure mode (falling out of the world beyond ~32 m), which is valuable for safe invocation.

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 front-loaded with the core purpose and then layers in practical constraints. It is somewhat long for a four-parameter tool, and the verification date is not essential, but most sentences contribute actionable context.

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?

For a tool with no output schema and no schema parameter descriptions, the definition covers the main behavior, safety implications, and spatial constraints well. It is still incomplete on mapPath and outputName semantics, which an agent would need to infer.

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%, so the description must carry the parameter burden. It explains the position and rotation arrays well, including degrees and that y is the heading, but it does not explicitly document mapPath or outputName, leaving two of four parameters only implied.

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 verb and resource: it sets the player spawn position and rotation in a copy of a save. It also distinguishes the tool from graph-based teleporting by explaining that this is the platform's way to place the player at level start.

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?

It gives clear usage context: use this to place the player at start instead of having a graph teleport them, and stay within about 30 m of the map center unless adding floor pieces. It does not explicitly compare against siblings like scene_add_respawn_point, so it stops short of full when/when-not guidance.

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