scene-add-editable-tilemap-layer

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

With no annotations, the description must carry the burden. It discloses that the tool adds both a layer to tilemap data and an EditableLayer game object to the scene. However, it does not mention prerequisites (e.g., existing editable tilemap) or side effects. The behavioral info is useful but incomplete.

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 five sentences with some redundancy (e.g., 'complexity' mentioned twice). It could be more concise while retaining key information. The most important action is front-loaded.

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 output schema, no annotations, and nested parameters, the description explains the tool's effect but lacks prerequisites, error conditions, and return value info. It covers the basic function but is not fully complete.

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?

The description adds value beyond the schema by noting that the layer name is used for code variable generation and that sceneId is a unique identifier requiring scene data. These details help the agent use parameters correctly.

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 clearly states the verb 'Add' and the resource 'editable tilemap layer'. It distinguishes from Tiled maps and hints at dedicated tools, but does not explicitly differentiate from specific sibling tools like 'scene-fill-editable-tilemap-layer-data'.

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 description mentions the complexity of editable tilemaps and that dedicated tools exist, but does not explicitly state when to use this tool versus alternatives. It provides context but no clear when-not or alternative references.

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