load_save_from_menu

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

Discloses time estimate (30-90 seconds), use of macOS Vision OCR, and that it's destructive (consistent with destructiveHint annotation). Adds useful behavioral context beyond the annotation.

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?

Structured with Args, requirements, and post-step. Compact but informative. A minor improvement could be integrating the pyobjc install note elsewhere.

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 prerequisites, time, method, and follow-up. Output schema exists, so return values are not needed. Adequate for the tool's complexity.

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 single parameter save_name is well-explained with an example and default behavior (loads most recent autosave). This adds meaning beyond the schema's optional string definition.

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 the action (navigate main menu to load a save via OCR-guided clicking) and distinguishes from other load tools like load_save by specifying the menu-based approach.

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?

Provides explicit prerequisites: game running and at main menu. Also gives post-load guidance to call get_game_overview. However, no direct exclusions or alternatives mentioned.

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