Open the map in the World Editor

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

Discloses no automation API and that it merely opens the file. Missing details on system requirements (Warcraft III must be installed), error handling if map or exe not found, and side effects (launches external process).

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?

Two efficient sentences. Front-loaded with action and purpose, followed by contextual caveat and parameter guidance. No fluff.

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?

No output schema. Adequate for a launch tool but could mention prerequisites (map existence, editor installation) and post-launch behavior. Missing how to verify success or failure.

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 covers both parameters. Description adds value by explaining exePath overrides auto-detection, which is not obvious from schema alone.

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?

Clear verb 'Launch', specific resource 'Warcraft III World Editor', and purpose 'so the user can see/verify the edits'. Distinguishes from siblings like wc3_test_map (test in game) and other editing tools.

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?

Implies use for visual verification but no explicit when-not-to-use or comparison with alternatives like wc3_test_map. Only guidance is 'pass exePath to override auto-detection'.

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