pixelart_suggest_tile_size

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

Annotations indicate readOnly, idempotent, non-destructive. Description adds default PPU, priority logic when category given, and fallback to 16x16. Describes return format. No contradiction.

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?

Well-structured: purpose first, then logic with bullet points, important warning, then args and returns. Every sentence adds value, no fluff.

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 all relevant context: default PPU, priority logic, screen resolution fallback, return format (JSON with fields), and links to related tools for next steps. Complete for the tool's complexity.

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 has parameter descriptions, but the tool description explains the decision logic (category takes priority, screen size fallback) that adds meaning beyond the schema, compensating for the 0% coverage metric.

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 it suggests a pixel size for ONE tile, distinguishing from a full tilemap/level. It differentiates from sibling tools like pixelart_suggest_tilemap_layout and pixelart_create_tileset by specifying it is a single tile only.

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 explicit when-to-use (suggest tile size) and when-not (never export a single tile-sized canvas as whole tilemap). Suggests next steps: pixelart_suggest_tilemap_layout and pixelart_create_tileset.

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