Update map properties

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

With no annotations, the description carries full burden. It discloses the shallow-merge behavior, refusal to modify certain fields, and tile editing unsupported. It does not mention permissions, idempotency, or if it returns updated map data, but the key behavioral traits are covered.

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 sentences: first states action and examples, second states limitations. No filler, front-loaded with the verb and resource, highly efficient.

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?

Given no annotations, no output schema, and 2 params, the description adequately covers purpose, acceptable fields, and exclusions. It does not explain return values or error states, but for a simple update tool this is sufficient.

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 has 2 params: mapId (integer) and data (object with additionalProperties). Description adds that data includes fields like displayName, note, bgm, encounterList, and that it refuses to set 'data' or 'events', which adds meaning beyond the schema's generic description of 'Map property fields to set'. Schema description coverage is 50%, but description compensates.

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?

Description clearly states it performs a shallow merge into a map's JSON, lists specific fields (displayName, note, bgm, encounterList), and explicitly distinguishes what it does not touch (data, events) and unsupported tile editing. This differentiates it from sibling tools like update_event and create_map.

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?

Provides clear when-not-to-use guidance: refuses to touch 'data' or 'events' (use dedicated event tools) and tile editing not supported. However, it does not explicitly state when to use this tool over alternatives like create_map or list_maps, though the context implies it for updating existing map properties.

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