Run the map in Warcraft III

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

No annotations are provided, so the description must fully disclose behavior. It fails to mention whether the tool blocks until the game closes, what happens if Warcraft III is already running, or error handling (e.g., missing exe). This omission is significant for a launch command.

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 sentences containing all essential information without extraneous text. Each sentence earns its place: first states the main action, second clarifies parameter usage.

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 tool with 3 parameters and no output schema, the description explains the primary function and two optional parameters. However, it lacks important behavioral context (blocking, error conditions) that would be needed for safe invocation, leaving it minimally adequate.

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 coverage is 100%, but the description adds value by explaining the purpose of optional parameters (exePath for override, windowed for fullscreen) and the default windowed mode, which goes beyond the schema's basic descriptions.

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 'Launch Warcraft III running the given map' with a specific verb and resource. It distinguishes itself from sibling tools which are mostly editing or reading operations, making it the only test/run tool.

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 provides context for when to use (to play changes immediately) and mentions optional parameters to override default behavior. It does not explicitly state when not to use or list alternatives, but the sibling set makes it clear this is the only tool for launching the map.

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