list-tiles

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

The description declares the tool is read-only and explains its purpose as a precursor to editing. With no annotations, this covers essential behavioral traits, though it omits details like potential error handling or performance limits.

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?

Two sentences with high information density, front-loaded with purpose and return details. No extraneous text.

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 (single parameter, no nested objects, no output schema), the description fully covers purpose, usage, and behavior. No gaps for a list tool.

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% with detailed description of sceneIdentifier. The tool description reiterates 'on a scene' but adds no new semantic value beyond the schema.

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 specifies the verb 'List', the resource 'Tiles', and the scope 'every Tile on a scene'. It also enumerates the returned fields (id, position, size, etc.), distinguishing it from sibling tools like update-tiles and delete-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?

Explicitly states this is read-only and the inspect step before update-tiles/delete-tiles, providing clear when-to-use guidance and signaling it should not be used for modification.

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