restart_and_load

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

Exposes detailed step-by-step sequence with timing estimates (60-120 seconds total), mentions OCR navigation, and advises post-completion verification. Adds significant context beyond the destructiveHint annotation, with no contradictions.

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?

Well-structured: one-line summary, Args section, use case, numbered steps. Every sentence serves a purpose, no fluff. Front-loaded with the most critical information.

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?

Covers all essential aspects for a complex, destructive, multi-step tool: purpose, when to use, duration, step breakdown, output verification. No gaps given the tool's nature and existing output schema.

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%, but the description fully explains the single parameter save_name: its format ('AutoSave_0221'), default behavior (most recent autosave), and purpose. This compensates for the schema gap.

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 clearly states 'Full game recovery: kill, relaunch, and load a save.' This distinctively combines multiple actions (kill, relaunch, load) into a composite tool for recovery, differentiating it from siblings like kill_game, launch_game, and load_game_save.

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?

Identifies explicit usage context: 'recommended tool for recovering from game hangs (e.g. AI turn processing stuck in infinite loop).' Does not explicitly state when not to use or list alternatives, but the context is clear and focused.

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