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

Adds real context beyond the annotations: the call is 'FREE', output is capped at 2048px, the preview uses canonical split-part clips and walking-surface draw order, and it explicitly disclaims playability proof. Annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true) cover the safety profile, so this extra rendering/limits context is genuinely additive.

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?

Front-loads the most decision-relevant fact ('FREE') and the core action, then packs mode selection, limits, and caveats into a few tight sentences. Slightly dense with semicolon-clauses, but no sentence is filler.

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?

With no output schema, the description carries the return-shape burden and does so adequately: it tells the agent an image is produced, that the image suffices for visual review, and that the preview does not prove playability. A note on what to do when rendering exceeds limits or fails would make it complete, but the essentials are present.

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 67% and the description adds meaning beyond it: the viewport-omitted overview mode, world-pixel viewport/scale usage, and the 2048px longest-edge cap with 'read returned scale for the effective value'. It does not restate every field, but it clarifies the viewport-vs-scale interplay that the schema only partially documents.

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?

States a specific verb ('Render') and resource ('the actual map composition') and scopes it with 'canonical terrain/export rendering'. It implicitly separates itself from commit_map_draft/export_map by saying 'before saving', but never names a sibling explicitly, so it lands at 4 rather than 5.

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?

Gives concrete usage conditions: omit viewport for an overview, supply a viewport+scale for camera-sized inspection, and 'inspect this image and fix problems before saving'. It also rules out a workflow ('without browser automation'). It stops short of naming the alternative tools (commit_map_draft, run_map_playtest), so no explicit when-not/alternative routing.

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