launch_game

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

Adds significant detail beyond the destructiveHint annotation: describes the ~15-30 second wait, that the game appears at main menu, and the connectivity limitation of FireTuner at main menu. These are critical behavioral traits for an AI agent.

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?

Three sentences plus a note, minimal but comprehensive. Purpose, timing, post-launch state, and limitations are all front-loaded. Every sentence serves a clear purpose with no redundancy.

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 zero parameters and presence of output schema (not detailed but indicated), the description fully covers launch behavior, post-launch state, next-step suggestions, and a known limitation. Everything an agent needs to invoke it 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?

No parameters in input schema, so description cannot add parameter details. Schema coverage is 100%, and the description appropriately focuses on the launch behavior rather than parameters.

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?

Clearly states it launches Civ 6 via Steam, specifying the action and resource. Differentiates from sibling tools like kill_game or load_save by describing the launch process and resulting main menu state.

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?

Explicitly advises using load_save or restart_and_load after launch for loading a specific save, and warns that FireTuner and in-game MCP tools are only available after a save is loaded. Could add when not to use (e.g., if already launched) but provides clear sequential context.

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