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

With no annotations, the description carries the full burden. It usefully discloses the price ($0.30 USDC via x402, charged only on success) and partial-update semantics ('untouched zones keep their tiles'), but says nothing about auth requirements, what happens to edited zones, or the return/result format.

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 compact sentences with the core action front-loaded and pricing appended second. No filler, though the trailing 'Part of Level design: Level dressing for 3D games' is somewhat boilerplate.

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 mutation tool with no annotations and no output schema, the description covers cost and partial-update behavior but leaves the most complex aspect — the nested edit rule grammar — unexplained. It is adequate but incomplete for an agent to invoke correctly without inspecting the schema closely.

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 0%, so the description must compensate for three parameters and it largely does not. It only alludes to 'instruction' and 'zone edits'; the rule kinds (scatter/along/cluster/stamp/anchor), densities, spacing, and radius semantics are entirely undocumented in both schema and description.

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 and resource ('Change a 2D map') plus the two modes of input (instruction or zone edits). The '2D' qualifier implicitly separates it from the 3D level_design_revise sibling, but 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?

Implies two usage modes ('by instruction or zone edits') and notes that untouched zones keep their tiles, which hints at partial-update intent. However, there is no explicit when-to-use vs alternatives guidance, nor prerequisites for choosing between level_design_revise, level_design_revise_2d, or level_design_place_2d.

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