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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavior: the result is rendered in the chat, the layer view is capped at the first 500 pins, and the no-argument list doubles as an interactive picker where the person can tick and delete maps. That last point is a mild tension with destructiveHint=false (the tool itself is still a read), but it is disclosed rather than hidden.

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?

The opening sentence is a dense pile-up of return fields, and the use-case guidance is spread across four later sentences with repeated "use it when" phrasing. Content is valuable and mostly front-loaded, but it is longer and less scannable than it needs to be.

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 full burden and does so: it describes the returned link, downloads, layers/pins, version history, the 500-pin truncation, and the listing mode, plus how each mode is triggered. An agent can call this correctly with nothing left to infer.

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 100%, so the baseline is 3, but the description goes further by explaining the semantic consequence of omitting map (list the person's own maps) and clarifies the special layer value "pins" for InstaMaps Sheets add-on maps. It adds meaning beyond the schema's terse parameter docs.

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 concrete verb+resource (read a kept map made with render_map) and enumerates the returned surface: link and downloads, layers with pin ids and fields, version and earlier versions, or a layer's pins. It is clearly distinguishable from render_map, update_map and delete_map, and it also states the zero-argument listing mode.

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 explicit when-to-use routing: call before update_map on a map from an earlier conversation, call with no arguments when the person asks to see their maps or supplies no link, and use the resulting list when they want to delete maps but haven't named them. Alternatives are named rather than implied.

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