Create map

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

With no annotations, the description carries full burden. It discloses file writes (MapXXX.json, MapInfos.json) and return value (new map id). It also explains limitations (tiles not paint-ready). Lacks mention of authorization or side effects, but adequate for a creation tool.

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 concise sentences with front-loaded main purpose. Every sentence adds value; no wasted words.

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 5 parameters and no output schema, the description explains the creation process and return value (id). It misses details on parameter semantics, but overall covers the key aspects of tool behavior.

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 20% (only parentId has a description). The description does not explain parameter meanings beyond implying name is used for the map file. Defaults and constraints are in the schema but not clarified, leaving ambiguity for an AI agent.

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 'Create a new blank map' and explains the concrete actions: writes MapXXX.json and registers in MapInfos.json. It distinguishes from other tools by specifying that tiles must be painted in the editor but events/properties can be edited here.

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 context on what can be done after creation (editing events/properties) and what cannot (tile painting). However, no explicit alternatives or when-not-to-use guidance is given, though sibling tools like update_map and create_event provide contrast.

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