Unity API Communicator MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about potential delays ('may take time') and the underlying process ('Unity reimports assets'), which helps set expectations. However, it doesn't cover other behavioral aspects like error conditions, permissions needed, or what happens to ongoing builds.

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 two sentences that are front-loaded with the core purpose and followed by important behavioral context. Every word earns its place, with no redundancy or unnecessary elaboration.

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 moderate complexity (changing build platforms with potential reimports), no annotations, and no output schema, the description is minimally adequate. It covers the basic action and a key behavioral trait but lacks details on outcomes, error handling, or integration with other build tools, leaving gaps for an agent.

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 input schema has 100% description coverage with a clear enum for the 'platform' parameter. The description doesn't add any semantic details beyond what the schema provides (e.g., it doesn't explain platform differences or dependencies). Since schema coverage is high, the baseline score of 3 is appropriate.

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 'switch' and resource 'active build platform', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'build_platforms' or 'build_player_settings', which might provide related functionality.

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 mentions 'This may take time as Unity reimports assets,' which implies a performance consideration but doesn't provide explicit guidance on when to use this tool versus alternatives like 'build_platforms' or 'build_player_settings'. No exclusions or prerequisites are stated.

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