unity_play_mode

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

No annotations are provided, so the description carries the full burden. It clearly states that the tool controls play mode (enter, pause, stop), which are mutating actions. It does not mention any side effects (e.g., unsaved scene changes) or preconditions (e.g., must be in edit mode). Adequate but could be more thorough.

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 very concise (one sentence), but it could be slightly more structured. The 'port' parameter's lengthy guidance is included in the schema description, which is acceptable. No wasted words.

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 that there is no output schema, the description does not need to explain return values. The tool is simple (2 params, 1 required). It covers the core functionality, but lacks information about potential errors or prerequisites (e.g., requiring an active Unity instance). Adequate for the 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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the 'port' parameter's purpose (target Unity instance, parallel-safe routing) and providing a reference to another tool (unity_select_instance). The 'action' enum is self-explanatory, but the description adds no extra semantics for it.

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 uses specific verbs ('enter', 'pause', 'stop') and a clear resource ('Unity Editor play mode'). It distinguishes from sibling tools by being the only one focused on play mode control. However, it could be more explicit about the scope (e.g., it controls the Editor's play mode, not runtime).

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 when you need to control play mode, but does not provide explicit when-not-to-use or alternatives. The 'port' parameter description gives usage guidance for multi-instance scenarios, which helps. No sibling tools are mentioned as alternatives.

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