Palette

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

The description goes beyond the bare annotations by describing operation effects: 'set' writes or replaces, 'ramp' appends a hue-shifted ramp, and 'analyze' reports palette issues. However, it does not disclose which operations are destructive or how replacing/remapping affects existing pixels, leaving meaningful behavioral gaps for a mutation-capable tool.

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 bulleted operation list is well organized and front-loaded, making the tool's capabilities scannable. The closing 'Decide the palette before drawing' advice is useful, though the artistic commentary about machine-made pixel art is slightly extraneous and could be trimmed without losing operational clarity.

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 tool with 11 parameters, six operations, and an output schema, the description plus schema provide a complete picture. The description covers each operation's purpose, key inputs, and output highlights, while parameter details are handled by the high-coverage schema. The workflow warning also helps the agent apply the tool correctly.

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?

With 91% schema coverage, the schema already documents most parameters, so the baseline is 3. The description adds value by mapping operations to their relevant inputs, e.g. 'load' reads .gpl/.hex/.pal/.png files, 'preset' lists bundled palettes, and 'ramp' describes base-colour behavior. This enriches parameter understanding beyond the raw 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's resource and action: 'Read and shape the sprite's palette,' and enumerates six distinct operations with concrete outcomes. It does not explicitly contrast itself with nearby siblings like 'recolor', but the operation list makes the scope understandable.

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 description gives practical workflow guidance: 'Decide the palette before drawing. Retro-fitting one onto finished art means repainting,' which tells the agent when in a workflow this tool belongs. It does not name alternative tools or explicitly say when not to use it, so it falls short of full routing guidance.

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