Start or stop a game session that stays up

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

Beyond the annotations, the description discloses important behavior: the session persists between calls, is paused at frame 0, is reachable only via a loopback port with a token, does not modify the project, stores its script under .godot/godotwright/, and auto-quits after idle_minutes. These details materially affect how and when an agent should use the tool.

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 covers operation modes, sibling comparison, security, and cleanup. It is dense but every sentence carries useful information, with no obvious filler.

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 complex lifecycle tool with no output schema, the description covers the important context: persistence, security, project isolation, idle shutdown, and operation modes. It does not describe what the `status` operation returns, which leaves a small gap for an agent invoking that op.

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 100%, so the schema already documents op, path, scene, restart, idle_minutes, and timeout_seconds. The description repeats defaults for scene, restart, and idle_minutes but adds little semantic detail beyond the schema, and it does not mention path or timeout_seconds at all.

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: load a Godot scene headless and keep the session running between calls, paused at frame 0. It explicitly distinguishes this from godot_play, which reloads the world on every call, so an agent can tell the two apart without opening schemas.

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 a clear use case: use this when godot_game needs a live game to inspect and step frame by frame, especially when loading is slow. It names godot_play as the reload-every-call alternative and says to stop the session when done, though it does not explicitly state when not to use it.

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