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

Annotations already flag destructive and idempotent, and the description goes well beyond them: a roughly 1 MB payload ceiling, the guarantee that the link and publish state survive, that old content is backed up, and that style is only replaced "if given". These are exactly the consequences an agent needs before triggering a destructive overwrite.

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?

Two dense sentences, front-loaded with the destructive action and the preserved state right after. Every clause carries information, though the list of replaced fields and the preservation note could be ordered slightly more crisply.

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 no-output-schema destructive tool this covers the essentials (scope of destruction, preservation, backup, payload limit). It stops short of stating authorisation requirements and what the call returns, minor gaps given the annotations.

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 50%: the map parameter is documented in the schema, mapId is not. The description adds real value for map (import format reference plus the ~1 MB limit) but says nothing about mapId beyond the notion of an existing map, so it only partly closes the 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?

States a specific verb ("Overwrite") plus the resource (an existing map) and enumerates exactly which parts are replaced: layers, markers, name, description, casualty bar, style. "Existing map" implicitly separates it from create_map, though no sibling is named explicitly.

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: the word "existing" and the preserved link/publish state tell an agent this is for an already-created map, but there is no explicit when-to-use vs create_map or get_import_format, and no stated preconditions (e.g. ownership or required permissions).

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