wow_play

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

Describes that actions are applied sequentially, stops early if episode ends, and returns total reward, end flags, and final state. No annotations provided, so description carries full burden; adequate disclosure of core behavior, though could mention state persistence.

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 focused sentences, no fluff, front-loaded with the core action. Each sentence contributes unique 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?

Given a simple tool with one parameter and no output schema, description fully covers behavior, return values, and batching rationale. Differentiates from siblings effectively.

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?

Single parameter 'actions' has full schema coverage, and description adds that they are ordered action names from wow_list_actions, providing useful context beyond the schema.

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 applies a sequence of named actions, one env step each. Distinguishes itself from sibling wow_step by emphasizing fewer round-trips via batching.

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 preferring batches of 1-10 actions to reduce round-trips, and mentions early stopping on episode end. Appropriate guidance, though does not explicitly mention when not to use (e.g., for single actions, use wow_step).

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