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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value by naming the returned state components, notably pending_changes and version, hinting this is a sync/read-current-state endpoint, but says nothing about cost, permissions, or the read-only nature of share_url access.

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 short, front-loaded sentence with no filler. The noun-list style is compact but slightly cryptic, since the fields are not labeled as return values.

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 an output schema present and 80% param coverage, the description need not explain return shapes, and annotations cover safety. However, for a 5-parameter tool with three mutually exclusive access modes (map_id, share_url, draft_handle) and a sync parameter, the description is too terse to help an agent pick the right mode confidently.

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 80%, with map_id, share_url, and since all documented in-schema, so the schema carries the semantic load. The description mentions version and pending_changes but does not connect them to the since parameter or explain the map_id/share_url/draft_handle selection, so it adds no meaning beyond the schema.

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 ("Read a map") and enumerates the state fields returned, so the agent knows this is a single-map full-state read. It does not explicitly contrast with siblings like map_list or map_search_places, and the bare noun "lists" could momentarily be confused with the map_list tool.

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?

No when-to-use or when-not-to-use guidance, and no alternatives named. The agent must infer from the name alone that this is the general "fetch current state" call versus map_list (enumerate maps) or map_search_places (partial lookup).

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