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 for behavioral disclosure. It states the tool changes a material's shader, implying a mutation operation, but doesn't disclose critical traits: whether this requires specific permissions, if changes are reversible, potential side effects (e.g., breaking material properties), or error conditions. The description is minimal and lacks behavioral context.

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 core purpose. It includes helpful examples without unnecessary elaboration. However, it could be slightly more structured by separating purpose from examples, but overall it's appropriately concise.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects (permissions, side effects), usage guidelines, or return values. Given the complexity of modifying materials in a game engine context, more context is needed to ensure safe and correct usage.

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%, with both parameters clearly documented in the schema (materialPath and shaderName). The description adds minimal value beyond the schema by providing shader name examples ('Standard', 'Universal Render Pipeline/Lit'), but doesn't explain parameter interactions or constraints. Baseline 3 is appropriate since the 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 action ('Change the shader') and target ('of a material'), with specific examples of shader names. It distinguishes from sibling tools like material_color, material_float, and material_texture by focusing on shader assignment rather than other material properties. However, it doesn't explicitly differentiate from material_properties which might overlap.

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. The description doesn't mention prerequisites (e.g., material must exist), when not to use it, or how it relates to sibling tools like material_properties or gameobject_material. Usage context is implied but not stated.

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