game_multimesh

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

No annotations provided, so description bears full burden. It only states 'Create/configure for instancing' without disclosing behavioral traits like node creation, destructiveness, or side effects. The action parameter hints at behaviors but description adds no extra 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?

Single sentence, no fluff, and front-loaded with verb and resource. However, could benefit from structured format like bullet points for actions.

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?

Despite full schema parameter descriptions, the description lacks context for a tool with 8 params and 3 actions. No explanation of action workflows or parameter relationships. Lacks completeness for complexity.

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 covers all 8 parameters with descriptions (100% coverage), so baseline is 3. Description adds no additional meaning or usage context beyond 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?

Description states specific verb 'Create/configure' and resource 'MultiMeshInstance3D for instancing', clearly indicating purpose. However, it does not differentiate from sibling tools like game_mesh_instance or game_3d_effects.

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 on when to use this tool vs alternatives. The description implies instancing use but doesn't mention when not to use or provide context for selecting this over other mesh tools.

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