wow_step

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

With no annotations, the description discloses the key behaviors: advancing by one env step (~0.25s), returning reward, end flags, and new state. It does not mention any destructive side effects or prerequisites, but the behavior is well described for a simulation step.

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?

The description is two sentences with no wasted words. The first sentence states the core action and timing, the second lists return values. It is front-loaded and efficient.

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 the simplicity of the tool (single parameter, no output schema), the description is complete. It explains what the tool does, how it advances, and what it returns. It could elaborate on 'end flags' or mention that the step consumes the action, but it is adequate for correct usage.

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% with the action parameter description. The description adds value by reinforcing that the action is a single named action and providing concrete examples (e.g., 'forward', 'attack'). This goes beyond the schema's description which only references wow_list_actions.

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 verb 'Take' and the resource 'ONE named action' to advance the sim. It distinguishes from sibling tools like wow_reset, wow_list_actions, and wow_state by specifying that it performs a single step and returns reward and state.

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 by mentioning 'action name from wow_list_actions' and giving examples of valid actions. It implies that wow_list_actions should be called first to get available actions. However, it lacks explicit guidance on when not to use this tool (e.g., for multiple steps or resets).

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