play_mode

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

The description implies mutation (controls) consistent with annotations (readOnlyHint: false). However, it does not disclose behavioral traits beyond what annotations provide, such as whether entering play mode recompiles scripts or affects unsaved scenes.

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 one sentence that lists all actions efficiently. It is front-loaded with the verb 'controls' and provides a clear list. No redundant 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?

For a simple tool with one parameter and no output schema, the description adequately covers the actions. It does not explain return values for 'get_state', but given the lack of output schema, this is a minor gap. Overall, it is complete enough for the tool's complexity.

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?

The schema already describes the single parameter 'action' with an enum and description. The tool description repeats the enum values but adds no additional meaning beyond what the schema provides. Schema coverage is 100%, so baseline of 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 explicitly lists the specific actions ('enter', 'exit', 'pause', 'unpause', 'step', 'get_state') and states it controls Unity Editor play mode. It clearly distinguishes from sibling tools like 'editor_control' which likely has a broader scope.

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 no guidance on when to use this tool versus alternatives such as 'debugger', 'playtest', or 'execute_menu_item'. There is no mention of prerequisites, context, or exclusions.

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