game_terrain

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Create/modify terrain meshes,' which reveals that the tool mutates or creates terrain, but it does not explain the multi-action dispatch behavior, side effects, requirements, or what happens without a proper node path. This is insufficient for a mutation-capable tool with no annotation safety hints.

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 concise sentence with no filler words. It is front-loaded with the core operation and resource. However, it is so sparse that it sacrifices useful detail, though that is more of a completeness concern than a conciseness problem.

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?

This is a complex tool with 13 parameters, multiple actions, and no output schema or annotations. The description covers only 'create/modify' and does not mention the query action, paint action, action-specific parameter requirements, return behavior, or prerequisites. An agent would need to infer too much from the schema alone.

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 no additional parameter meaning beyond the schema. It does not explain action-specific parameter groupings, which would be helpful given 13 parameters and a required 'action' field, but the schema already documents each parameter individually.

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 states a clear verb and resource: 'Create/modify terrain meshes from heightmap data.' It distinguishes this from sibling mesh/tilemap tools by focusing on terrain and heightmap. However, it omits the 'get_height' and 'paint' actions that the schema exposes, so the full purpose is not completely captured.

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?

There is no guidance on when to use this tool versus alternatives like game_tilemap, game_gridmap, or game_procedural_mesh. The description implies terrain-related usage but provides no explicit context, exclusions, or conditions that would help an agent choose it correctly.

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