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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds no explanation of what that destruction means — e.g. that unspecified fields are untouched while context with mode=replace overwrites prior text. The concurrency behavior (conflict with another's changes) is documented only in the schema's expected_version, not in the description, so the description contributes little beyond the annotation profile.

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 no filler; every item in the enumeration corresponds to a real parameter. Nothing is redundant or buried.

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?

For a 10-parameter destructive mutation with a nested object and no output schema, the description omits the two behaviors an agent most needs: optimistic-concurrency conflict handling via expected_version, and draft-map targeting via draft_handle. It also never states what a successful update returns or whether a version is echoed back.

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?

The description names six of the ten parameters' purposes, which usefully signals that any subset of settings may be changed (matching the anyOf). However, map_id, draft_handle, conversation_id, and expected_version go unmentioned, and the schema already carries rich descriptions for context, day_noun, route_stops, draft_handle, and expected_version at 50% coverage — so the description adds modest value over 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?

The description gives a specific verb ("Change") and resource ("a map") and enumerates the mutable settings — title, context, travel mode, interests, day noun, route_stops — which lets an agent distinguish this map-level settings tool from map_edit_lists and map_edit_places. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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 or when-not-to-use guidance: nothing says to prefer map_edit_places for place edits or map_edit_lists for list edits, and nothing about draft maps versus saved maps or when expected_version is required. Usage is only inferable from the field list.

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