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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by enumerating the returned content (keyframes, layers, iframe code), but discloses nothing about failure modes — e.g. what happens when the map is unpublished or not found, or whether URL vs handle/slug have different resolution rules.

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?

One dense sentence that front-loads the output contract and ends with invocation. Nothing is wasted, though the run-on list of returned fields is slightly harder to scan than a short structured form.

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-value burden and does so thoroughly, and annotations cover the read-only profile. Remaining gaps are minor: error behavior and disambiguation of the handle/slug alternative are not covered.

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 33%, so the description must compensate — and it does by clarifying the two identification modes: either the full URL, or the handle plus slug pair. Only the url parameter is documented in the schema. It still leaves 'username' unnamed as the handle, but the pairing logic is genuinely additive.

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 and resource ('One published map') and enumerates exactly what the response contains: description, sources, keyframe timeline, layers, events, and iframe embed code. The singular scope implicitly separates it from search_maps, though the sibling is never named.

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?

'Pass its URL, or the handle and slug' explains how to invoke, but there is no statement about when this tool applies versus search_maps (e.g. 'use when you already have the map's URL, otherwise search first'). Usage is implied rather than specified.

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