Unity API Communicator MCP Server

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 describes the core behavior (focusing camera on selected GameObject) and provides a helpful real-world analogy. However, it doesn't disclose potential side effects (e.g., what happens if no GameObject is selected), performance implications, or error conditions, which would be valuable for a tool with zero annotation coverage.

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 a single, efficient sentence that immediately communicates the tool's purpose. The 'equivalent to pressing F' analogy adds valuable context without unnecessary elaboration. Every word serves a clear purpose, making it front-loaded and zero-waste.

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 zero-parameter tool with no annotations and no output schema, the description provides adequate context about what the tool does and when to use it. The analogy to a keyboard shortcut adds practical understanding. However, it could be more complete by mentioning what happens if no GameObject is selected or describing the visual result in the Scene View.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and usage. This meets the baseline expectation for zero-parameter tools.

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 states the action ('Focus the Scene View camera'), the target ('currently selected GameObject'), and provides a helpful analogy ('equivalent to pressing F'). It clearly distinguishes this tool from sibling tools like selection_get, selection_set, or camera_configure by specifying its unique camera-focusing function.

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 context: it should be used when a GameObject is selected to focus the camera on it. However, it doesn't explicitly state when NOT to use it (e.g., if no GameObject is selected) or name alternative tools for related functions, though the 'equivalent to pressing F' analogy provides practical guidance.

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