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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the payload includes a downloadable link with a 15-minute expiry and warns the JSON can be several MB, which matters for how an agent handles the result. It stops short of saying whether the link is single-use or what happens on expiry.

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 sentence, front-loaded with what is returned and followed by the caveat about the download link. Nothing is wasted, though the nested clause in the middle makes it slightly dense.

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 must describe the return value and does so adequately: a summary of layers, keyframe dates and markers plus an expiring download link for full JSON. An agent knows what it gets and roughly what to expect size-wise; only link lifecycle details are missing.

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 100% for the single mapId parameter, so the schema carries the parameter burden. The description never mentions mapId or its format, adding nothing on parameters — the baseline 3 applies.

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 names a specific verb+resource ('summary of one of the user's maps') and enumerates the returned fields (layers, keyframe dates, markers), which tells an agent this is a single-map fetch. It does not explicitly contrast with siblings like list_maps, get_public_map, or search_maps, so differentiation is left to inference.

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?

Usage is only implied: fetch a single map by id, as opposed to listing/searching. There is no explicit statement of when to prefer this over get_public_map or search_maps, nor any prerequisites such as ownership or auth.

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