game_tilemap

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

No annotations are present, so the description must carry the full burden of disclosing behavioral effects. 'Get or set cells' says nothing about whether erase_cells is destructive, whether set_cells overwrites existing cells, whether sourceId is required for placement fidelity, or what happens with invalid coordinates. The action values reveal intent in the schema, but the description itself provides no behavioral safety or side-effect information.

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 clear sentence with no filler or redundancy, making it easy to parse quickly. It is arguably too terse for a multi-action tool, but the front-loaded verb-resource structure is effective. A slightly more detailed sentence describing the available actions would improve comprehensiveness without harming conciseness.

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 tool has six parameters, four distinct actions, no output schema, and no annotations, making it a fairly complex tool for the description to support. The one-sentence description does not mention return behavior for get_cell or get_used_cells, the expected shape of cell objects in the cells array, or any constraints on nodePath and sourceId. Given the complexity, the description is incomplete for guiding an agent to call all actions correctly.

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 and the description does not need to repeat parameter definitions. The description adds no meaning beyond the schema: it does not clarify the structure of cell objects, the coordinate system, or how sourceId interacts with get_used_cells. Since the schema already explains each parameter at a basic level, the description's minimal contribution is acceptable but not additive.

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-resource relationship: 'Get or set cells in a TileMapLayer node.' It identifies the target Godot node type and the general operation domain, and the action parameter further disambiguates among cell operations. However, it does not enumerate the full set of operations such as erase_cells or get_used_cells, relying on the input schema to communicate the complete scope.

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 implies usage through the tool name and reference to TileMapLayer nodes, which distinguishes it from sibling tile-related tools like game_gridmap or game_terrain. There is no explicit guidance on when to prefer this tool, when not to use it, or what prerequisites exist (e.g., a TileMapLayer node must already exist). The action field provides some operational context, but alternatives and exclusions are not stated.

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