Render a native tile-layer map preview

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds substantial behavioral detail: it does not invoke TmxRasterizer, requires explicit region for infinite maps, highlights must intersect tileRegion, object visibility/opacity is ignored, text glyphs are not rendered, and embedded tilesets fail closed. No contradictions with annotations.

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 technically detailed, front-loading the core action but then listing many specifics. While every sentence adds value, the length and complexity could be streamlined for quicker comprehension.

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 (5 parameters, nested objects, output schema exists), the description covers most key aspects: profiles, region handling, constraints, and limitations. However, it lacks mention of output format/return value and does not explain scale or layerIds, leaving some gaps.

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 only 20% (only mapPath has a description in the schema). The description compensates by explaining region and overlays in depth (e.g., highlights must intersect region, object debug profiles), but does not cover scale or layerIds parameters. Thus, it adds moderate value beyond the schema but not enough for full clarity.

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 orthogonal TMJ region without invoking TmxRasterizer. It specifies the resource (TMJ region) and action (render), and distinguishes from sibling tools like tiled_render_isometric and tiled_render_hexagonal by focusing on orthogonal map preview and explicitly mentioning the absence of rasterizer invocation.

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 clear context on when to use this tool (for bounded orthogonal map previews, with explicit region for infinite maps) and what it supports (native v1 profile, fixed highlights, object debug). It states limitations like ignoring visibility/opacity and not rendering text glyphs, but does not explicitly list alternative tools for other cases.

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