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 discloses the action ('Open/load') and the path requirement, but lacks details on permissions, error handling (e.g., if path is invalid), or what happens to the current scene. It adds some context but misses key behavioral traits for a mutation tool.

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 front-loads the core action ('Open/load an existing scene') and provides essential details (asset path example). There's zero waste, making it appropriately sized and well-structured for quick understanding.

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 no annotations and no output schema, the description is minimal but covers the basic action and parameters. However, for a mutation tool that loads scenes, it lacks details on side effects (e.g., scene state changes), error scenarios, or return values, leaving gaps in completeness for safe agent use.

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 the schema already documents both parameters fully. The description mentions the path parameter with an example, but doesn't add meaning beyond what the schema provides (e.g., no extra context on path validation or mode implications). Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Open/load') and resource ('an existing scene'), specifying it's identified by its asset path. It distinguishes from siblings like scene_create (creates new), scene_close (closes), and scene_save (saves), making the purpose specific and differentiated.

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 by mentioning 'existing scene' and the path format, but doesn't explicitly state when to use this tool versus alternatives like scene_create for new scenes or scene_setactive for switching active scenes. No exclusions or prerequisites are provided, leaving usage context partially implied.

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