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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds nothing beyond that: no mention that saving requires an authenticated traveler, no explanation of what happens to an unsaved draft, and no note about failure modes for invalid map_id.

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 with zero wasted words. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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?

This is a mutation tool with no output schema and two parameters, one of which encodes a non-obvious draft-versus-saved distinction. The description never explains the draft path, expected return, or error behavior, leaving an agent unable to call it correctly in the unsaved-map case.

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 only 50%: map_id carries a pattern but no description, and draft_handle documents itself. The description discusses neither parameter, not even the crucial point that draft_handle applies only to unsaved maps, so it fails to compensate for the coverage gap.

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?

"Save a map to the traveler's account" gives a specific verb (save) and resource (map) with target scope (the account), which distinguishes it from map_create (draft creation) and map_share. It stops short of naming any sibling explicitly, so the agent must infer the create-vs-save boundary.

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?

There is no when-to-use guidance at all: nothing says whether the map must already exist, whether this is the follow-up to map_create, or when map_update would be preferred instead. The only usage signal comes from the schema, not the description.

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