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 full burden. It mentions saving behavior but lacks details on permissions, overwrite risks, file format, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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?

Two sentences, zero waste. Front-loaded with core purpose, followed by optional parameter context. Every word earns its place without redundancy or fluff.

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 single-parameter mutation tool with no annotations and no output schema, the description is minimally adequate. It covers the basic action and parameter intent but lacks details on behavioral traits, error cases, or output expectations. Given the simplicity (1 param, 100% schema coverage), it's complete enough for basic use but could be more informative.

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 the single parameter ('path'). The description adds marginal value by clarifying that omitting the path saves in place and mentioning 'Save As' context, but doesn't provide syntax or format details beyond what the schema provides. Baseline 3 is appropriate when 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 ('Save') and resource ('the active scene'), with an optional 'Save As' functionality. It distinguishes from siblings like scene_close, scene_create, and scene_open by focusing on persistence rather than lifecycle management. However, it doesn't explicitly differentiate from asset operations like asset_create or asset_move, which could also involve saving.

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 saving the current scene, with an optional path for 'Save As' scenarios. It doesn't provide explicit when-not-to-use guidance or name alternatives among siblings (e.g., asset_create for non-scene assets). The context is clear but lacks exclusion criteria or prerequisite mentions like needing an open scene.

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