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 full burden but offers minimal behavioral context. It mentions 'optional' parameters but doesn't disclose what happens if parameters are omitted (defaults apply), whether the camera becomes active, if it's added to the scene hierarchy, or any permission requirements. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps.

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, well-structured sentence that front-loads the core purpose and efficiently lists parameter categories without redundancy. Every word serves a purpose, and there's no wasted verbiage 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 (creation with 6 optional parameters), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers what the tool does and parameter categories but lacks behavioral context, usage guidance, and output information. For a creation tool in this context, more completeness would be expected.

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 all 6 parameters thoroughly. The description adds marginal value by grouping parameters into categories ('optional position, FOV, and orthographic mode') but doesn't provide additional semantics beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 specific action ('Create a new Camera GameObject') and resource ('in the scene'), distinguishing it from sibling tools like camera_list, camera_configure, or camera_capture. It specifies the exact type of object being created (Camera GameObject) rather than just 'camera'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an open scene), compare to similar creation tools like gameobject_create, or indicate when orthographic vs perspective cameras are appropriate. The description only states what it does, not when to choose it.

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