export_godot_tileset

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

No annotations are provided, so the description carries the full burden. It states the tool generates a file but does not disclose whether it overwrites the output path, requires specific image formats, or has other side effects. This is a significant gap for a tool that writes resources.

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 single, focused sentence that front-loads the action and purpose. It is concise with no unnecessary words or repetition.

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?

The tool is relatively simple with full schema coverage, and the description covers the core purpose. However, without annotations or output schema, it lacks information about overwrites, prerequisites, or return values, making it adequate but not 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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description itself doesn't add much beyond the schema, but it does provide context for how parameters relate to the tile sheet and output path.

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 uses a specific verb ('Generate') and clearly identifies the resource (a Godot 4 TileSet .tres) and input (tile sheet). It explicitly mentions the intended use with TileMapLayer, distinguishing it from sibling export tools like export_godot_spriteframes.

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 provides clear context for when to use the tool ('For use with TileMapLayer'), which implies the target scenario. However, it does not offer explicit alternatives or exclusions compared to other export tools, such as export_sprite_sheet.

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