get_tile_at

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

The description clearly states it is a read operation (no side effects) and explains the return value including that tile_index 0 means empty. With no annotations, it adequately discloses behavior.

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 concise with a clear structure: summary line, args list, returns line. No extraneous words, front-loaded with purpose.

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?

Given the tool's simplicity, no output schema, and 5 parameters, the description covers all necessary information: input details and output format. It is fully 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?

Each of the 5 parameters is described with its purpose, type, and constraints (e.g., frame_index starting at 1, col/row 0-based), adding significant value beyond the bare schema which has 0% description coverage.

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 tool reads which tile is at a grid position (specific verb and resource). It is distinct from siblings like set_tiles or draw_on_tile as a read operation.

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 use when needing to query a tile at a position but does not explicitly state when to use this tool versus alternatives like get_tilemap_info or draw_on_tile.

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