unity_play_mode

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

With no annotations, the description carries full burden. It discloses the basic actions (play, pause, stop) but does not detail side effects like scene running, state changes, or prerequisites. The behavior is straightforward but incomplete.

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?

Single sentence, perfectly front-loaded with the verb and resource. Every word earns its place—no redundancy.

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?

Despite minimal annotations and no output schema, the tool is simple with full schema coverage. The description adequately covers the core purpose. Missing return value details are acceptable for an action-oriented tool.

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 descriptive parameter descriptions. The description adds no additional meaning beyond the schema—it essentially restates the enum values. Baseline 3 is appropriate.

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 tool controls Unity Editor play mode with specific actions (enter play, pause, stop). It directly addresses the resource and verb, distinguishing it from sibling tools like unity_editor_state or unity_execute_menu_item.

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 implies usage for controlling play mode but provides no explicit guidance on when to use it versus alternatives. No exclusions or alternative tool mentions are given, leaving the agent to assume it's for standard play mode control.

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