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 earns credit by being the sole disclosure of the return payload (Markdown body, keyframe timeline, layers, events, iframe code), standing in for the missing output schema. It does not mention whether unpublished/private maps are rejected or what an invalid URL/handle produces.

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: return contents first, invocation second. Every clause carries information — the payload list and the two calling modes — with no 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 supplies the return shape thoroughly, which is the main burden here. Gaps are minor: no failure behavior, no statement of what an unpublished or nonexistent map returns, and no confirmation that zero arguments is not a valid call despite required params being empty.

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% — url has an example, slug and username have nothing. The description partially compensates by presenting two input modes (URL alone, or handle+slug), but it never states that 'handle' maps to the `username` field, nor whether both of those are jointly required, leaving ambiguity at the exact point the schema is weakest.

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?

Names a specific verb and resource ('One published map as Markdown') and enumerates exactly what comes back (description, sources, keyframe timeline, layers, events, iframe embed code). The word 'published' is the only signal separating it from the sibling get_map, which is a reasonable but unstated distinction.

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' tells the agent how to call it but not when to prefer it over get_map, list_maps, or search_maps. Usage is implied by 'published map' rather than stated, and there are no exclusions or prerequisites.

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