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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes the content of the render (preview, delivery state, canonical link), which is useful, but omits whether the map must already be activated via geobble_map_publication_activate or what happens for an unpublished mapId.

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?

A single front-loaded sentence with no filler; the verb and the returned artifacts appear immediately. It is efficient, though arguably too terse to carry the missing usage and parameter context.

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 does the right thing by naming what the render returns (preview, delivery state, canonical link) and annotations cover safety. However, the required mapId is undocumented and there is no guidance on the publication precondition, leaving gaps for an agent acting among many map_* and publication_* siblings.

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 0% and the single required parameter mapId has no description in either the schema or the description text. The phrase 'published map' hints that mapId refers to a published map, but the format constraint (UUID), whether it is a project/map/publication identifier, and what happens with an invalid or unpublished ID are all left unstated.

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 ('accessible published map') and enumerates what is surfaced: preview, delivery state, and canonical link. It is clear on its own, but it never distinguishes itself from the very similar sibling geobble_map_get, so an agent cannot tell the two apart from the text alone.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent must infer from the name that this is the tool for displaying an already-published map rather than fetching raw map data via geobble_map_get.

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