Import skin PNG

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

Annotations establish read-only, idempotent, non-open-world behavior. The description adds useful behavioral detail beyond that: conversion produces one layer per painted face and palette keys c01…cNN, with player-skin defaults and layout-specific outputs. It stops short of covering error or permission behavior, but the annotations carry the safety profile.

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 front-loaded with the core conversion action, then covers default behavior, layout overrides, and a brief post-import note. Every sentence contributes to correct invocation or expected output understanding.

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?

With annotations covering safety and an output schema covering return values, the description needs only to explain the operation, default layout, and output structure. It does all three, including the editable-spec format and palette-key convention, leaving no critical gaps for correct invocation.

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%, so the schema already documents path and layout. The description still adds value by clarifying the default player-skin dimensions (64×64 or legacy 64×32) and expanding the layout options beyond the schema's examples to mob, armor, cape, item, and block textures.

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 states a specific verb and resource: "Convert an existing PNG in the workspace into an editable spec." It also clarifies the default player-skin scope and the layout override, so an agent can tell this apart from siblings like texel_render or texel_save.

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 implies when to use the tool via "Convert an existing PNG ... into an editable spec" and explains the layout parameter's role. However, it does not explicitly compare the tool with alternatives such as texel_patch or texel_render, so usage guidance remains inferred rather than direct.

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