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

With no annotations, the description carries the full burden; it usefully discloses that size is preserved and the return is a PNG, which are genuine behavioral facts. However it omits what happens with transparency/alpha, whether dithering occurs, how the two image source parameters interact, and any size or rate limits (those live only in the schema).

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?

Three short sentences totalling under 30 words: operation first, then the invariant (size kept), then the return value. Every sentence earns its place and nothing is buried.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description covers purpose, the key invariant, and the return type. The one real gap is that the mutual exclusivity of image_url and image_base64 is not stated anywhere, which could lead to a malformed call.

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 description coverage is 100%, so all three parameters are already documented in detail, including palette format examples and image constraints. The description's '(e.g. PICO-8 or Game Boy)' only loosely echoes the schema's palette list and adds no new constraint semantics, so baseline 3 applies.

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?

States a specific verb (recolour) and resource (pixel art image) with the target resource (a palette), and clarifies the operation is a remap onto a constrained colour set. It is clearly not palette extraction or listing, though it never names the sibling tools to cement the distinction.

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?

The phrase 'an existing pixel art image' implies the precondition (you must already have an image, unlike generation-style siblings), but there is no explicit when-to-use/when-not, and no mention of extract_palette or list_palettes as the alternatives for palette discovery.

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