Inspect one map cell

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

With no annotations, the description carries the full behavioral burden, and it does establish this as a pure read and discloses the complete returned payload, which is the key behavioral fact. It omits edge-case behavior (out-of-bounds coordinates, nonexistent mapId) and any error or permission notes.

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?

One front-loaded sentence with the verb first and zero filler. Every clause earns its place by naming a returned data category.

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?

There is no output schema, and the description usefully enumerates the return contents, which is appropriate. However, for a 3-parameter tool with zero schema descriptions it leaves parameter meaning and usage context unaddressed, so it is only minimally complete.

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 0% and none of the three required parameters have descriptions. 'Single cell' weakly implies x/y identify the cell, but the coordinate space, bounds, and the meaning of mapId are never explained, so the description does not compensate for the schema gap.

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?

Specific verb ('Read') plus a precise resource ('a single cell') and an enumeration of exactly what is retrieved: tile layers, shadow bits, region id, terrain tag, and the event on the cell. This distinguishes it clearly from bulk siblings like get_map, render_map, and describe_tiles.

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 statement of when to use this versus alternatives such as get_map (whole map) or describe_tiles (tileset metadata), and no preconditions. The agent must infer from the name alone that this is the single-cell inspection tool.

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