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

The annotations declare destructiveHint=false, but the description explicitly states that mode replace 'overwrites an existing map's content,' which is a destructive update. The description adds useful details such as the 2-hour validity window, but this direct conflict with the annotation requires flagging.

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 description is two tightly written sentences with no filler. The core workflow and mode behavior are front-loaded, making it easy for an agent to parse.

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?

It explains the upload opening and the 2-hour validity window, but omits crucial workflow context such as uploading parts with upload_map_part and completing the upload with finish_map_upload. For a start step in a multi-tool chunked upload flow, that leaves the agent to infer the next required calls.

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 100%, so both mode and mapId are already documented in the schema. The description reinforces the replace behavior but adds no syntax, constraints, or defaults beyond what the schema provides.

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 uses a specific verb and resource: it opens an upload for map JSON sent in numbered parts. It distinguishes the tool from network-based uploads and explains create versus replace behavior, though it does not name sibling tools such as create_upload_link or replace_map_content 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?

The usage context is implied: use this when sending map JSON in numbered tool-call parts rather than over the network. However, the description gives no explicit when-not guidance and does not name the alternative sibling tools for direct creation, replacement, part upload, or finishing the upload.

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