Preview a native TSX write

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

Describes failure modes (grid derivation, per-tile metadata, etc.) and the expiring change set lifecycle. Annotations indicate readOnlyHint=true, which is consistent with a preview generating a change set.

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?

Single paragraph with front-loaded action and necessary details; no redundancy, though could be slightly more succinct.

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?

Covers key aspects: operation, constraints, return type, and application behavior. Output schema exists, so return value explanation is not required.

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% with descriptions. Description adds context about targetPath needing to be a new file in the source directory, enhancing understanding beyond the 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 clearly states the tool serializes a .tsj tileset to TSX bytes matching Tiled 1.12.2, distinguishing it from siblings like preview_write_tmx and preview_write_tx.

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 specific usage constraints (target must be new file in source tileset's directory) and notes no Tiled CLI is involved, but does not explicitly guide when to use vs. alternatives.

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