Render an isometric tile-layer preview

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

The description aligns with annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) and adds specific behavioral details: exact placement math, cells composite in diagonal scanline order, tile images anchor bottom-left, failure modes for unsupported features, and object layers skipped with ids disclosed. No contradictions.

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 dense and efficient, front-loading the main purpose in the first sentence. Every sentence adds necessary detail (rendering math, supported/failed features, sibling reference). No extraneous 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?

Given the tool's complexity (isometric rendering with many constraints) and the presence of an output schema, the description covers all essential aspects: what it renders, how it renders, supported tilesets, failure modes, and sibling differentiation. It is complete for an agent to correctly select and invoke the 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 only 25%, meaning most parameters lack descriptions. The description does not add meaning to individual parameters beyond what's in the schema (only mapPath has a description). It does not explain region, scale, or layerIds specifically. Given the low coverage, the description should compensate but does not.

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 renders a bounded region of a finite isometric TMJ map using Tiled's exact math. It specifies the rendering details (diamond region, diagonal scanline order, bottom-left anchor) and distinguishes from the sibling tool tiled_render_preview for orthogonal maps.

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 provides a clear when-not condition: 'Orthogonal maps belong to tiled_render_preview.' It also lists cases that 'fail closed' (image-collection tilesets, transparent-color keying, etc.), helping the agent avoid misuse. Implicitly, the tool is for isometric tileset-based maps, but explicit positive usage could be stronger.

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