Create a finite orthogonal TMJ map

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds behavioral details: it is a direct mutation without preview, will not overwrite existing files, and requires parent directories. This adds value beyond annotations.

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 only two sentences, efficiently conveying core behavior and conditions. The first sentence could be clearer, but overall it is concise with no unnecessary 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?

Despite having an output schema, the description does not explain return values or success criteria. Given the complexity of a creation tool and low parameter coverage, the description omits important context about what happens on success or error.

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 17% (only mapPath has a description). The tool description does not describe any parameters, failing to compensate for the low coverage. Width, height, tileWidth, tileHeight, and backgroundColor are undocumented.

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 states it creates an empty TMJ map, which is distinct from sibling creation tools like tiled_create_tileset or tiled_create_layer. However, the phrasing 'sole additive no-preview mutation exception' is cryptic and reduces clarity slightly.

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?

Conditions like 'parent directories must exist' and 'never overwritten' are given, but there is no explicit guidance on when to use this tool over alternatives. The context of map creation is implied but not directly compared to siblings.

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