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 insight. It implies mutation ('configure') but doesn't disclose permissions needed, whether changes are reversible, error conditions (e.g., invalid camera name), or side effects. It mentions properties but not how partial updates are handled or default values.

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 enumerates key properties without redundancy. Every word contributes to understanding the tool's scope, making it appropriately sized with zero waste.

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 incomplete for a mutation tool with 7 parameters. It lacks behavioral context (e.g., safety, errors), usage prerequisites, and output expectations. While concise, it doesn't compensate for the missing structured data, leaving gaps in understanding how to invoke it effectively.

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 parameters are well-documented in the schema. The description adds marginal value by listing property types (FOV, clip planes, etc.), which aligns with schema parameters but doesn't provide additional semantics like valid ranges, interactions (e.g., orthographicSize only matters if orthographic is true), or examples beyond what the schema already specifies.

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 action ('configure') and target ('existing camera's properties'), listing specific properties like FOV, clip planes, orthographic mode, background color, and depth. It distinguishes from siblings like camera_create (creation) and camera_capture/camera_screenshot (capturing), but doesn't explicitly differentiate from potential configuration overlaps in other tools.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., camera must exist), exclusions (e.g., not for creating cameras), or compare with sibling tools like camera_create or gameobject_component_add for similar functions.

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