game_tilemap

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

With no annotations, the description only implies read/write behavior. It does not disclose side effects, permissions, performance implications, or any constraints (e.g., need for an active scene).

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 sentence that efficiently communicates the core purpose. It is front-loaded and contains no unnecessary words.

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 the schema covering parameters well, the description is too brief for a tool with 6 parameters and multiple actions (set_cells, get_cell, erase_cells, get_used_cells). There is no output schema, and the description does not explain return values or how to use the different actions.

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 coverage is 100% (all parameters documented in the schema). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 ('get or set cells') and specifies the resource ('in a TileMapLayer node'), distinguishing it from sibling tools like game_gridmap which deal with gridmaps.

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 like game_gridmap or other game_* tools. There are no exclusions or context hints for the four different actions.

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