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 what information is returned but does not disclose behavioral traits like whether it requires specific permissions, if it's read-only (implied by 'Get'), error conditions, or performance considerations. The description is accurate but lacks depth for a tool with no 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 front-loads the purpose and lists the specific data returned. Every word earns its place, with no redundancy or unnecessary elaboration, making it easy to parse quickly.

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 the tool's simplicity (0 params, no annotations, no output schema), the description is adequate but minimal. It explains what is returned but does not cover format details, potential errors, or integration with sibling tools. For a read-only tool with no structured metadata, more context could enhance usability.

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 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description does not add param details beyond the schema, but this is appropriate given the lack of parameters. Baseline is 4 for 0 params, as the description focuses on output semantics instead.

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 'Get' and the resource 'currently active scene', specifying exactly what information is retrieved: name, path, build index, dirty state, and root object count. It distinguishes itself from siblings like scene_loaded (which lists loaded scenes) or scene_setactive (which changes the active scene).

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 information about the active scene is needed, such as checking its state or properties. However, it does not explicitly state when to use this tool versus alternatives like scene_loaded or project_info, nor does it mention prerequisites or exclusions.

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