game_multimesh

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

With no annotations for destructive or read-only hints, the description must disclose behaviors but only says 'Create/configure'. It implies mutation for create/set_instance and reading for get_info, but does not explain side effects, required permissions, or state changes.

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 extremely concise (one short sentence) and front-loaded with the core purpose. Every word adds value, though it could be slightly more detailed without bloating.

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 complexity (8 parameters, nested objects, multiple actions) and no output schema, the description is too sparse. It fails to explain the action parameter's role, the transform structure, or what get_info returns, leaving agents without essential context.

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 baseline is 3. The description adds overarching context ('for instancing') but no additional meaning beyond the schema's parameter descriptions. It does not compensate for missing details in the schema.

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 uses a specific verb ('Create/configure') and resource ('MultiMeshInstance3D') with context ('for instancing'). It clearly distinguishes from sibling tools like game_mesh_instance and game_procedural_mesh by focusing on the MultiMesh node type.

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 does not mention exclusions, prerequisites, or scenarios where other tools (e.g., game_mesh_instance) would be more appropriate.

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