create-tiles

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

With no annotations, the description is the sole source of behavioral info. It discloses per-tile error isolation, 404 warnings, return of created IDs, and GM-only restriction. It also explains occlusion mode semantics, adding useful transparency.

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 a dense single paragraph that front-loads the main purpose and then details parameters. It is efficient, though it could be slightly more structured for easier scanning.

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 the complexity (many optional parameters, nested objects, no output schema), the description covers essential behavior, return value, and error handling. It is sufficient for an agent to understand usage without additional info.

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 coverage is 100%, but the description adds context beyond parameter descriptions, e.g., clarifying that width/height are canvas pixels and referencing get-scene-dimensions for coordinate math. It explains occlusionMode values and video behavior, enhancing schema.

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 specifies the tool places TILES (props, roof pieces, decals, video overlays) on a scene from Data-relative image paths, clearly distinguishing it from siblings like create-drawings or create-lights.

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?

It correctly indicates GM-only usage and lists tile types, but does not explicitly state when to avoid this tool or mention alternatives. The context of sibling tools implies its specific role, but guidance is implicit.

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