Get or set palette

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 does not say whether switching a palette is persistent, whether it rewrites existing sprite colors, whether it requires a selected project, or what the response contains. 'Switch' and 'install' imply project mutation but no consequences or side effects are disclosed.

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?

Two compact sentences with no wasted words, and the read mode leads. It loses a point only because the trailing 'also lists...' clause is tacked on and competes with the main purpose rather than being framed as a mode.

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 has four parameters, multiple implicit modes, no annotations and no output schema, so the description should explain mode selection and mutation effects — it does neither. For a set/install-capable tool with zero structured behavioral hints, this is significantly under-specified.

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 75% and already documents `name`, `colors` (including the transparency-at-index-0 rule) and `project`. The description adds essentially no parameter meaning beyond saying 'combine with name to install a custom palette,' and the undocumented `description` parameter is ignored entirely in both schema and description.

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 packs three distinct operations (inspect, set built-in, install custom) plus a fourth (list semantic color roles) into one sentence, so the verb/resource is stated but the tool's primary purpose is muddled. It never clarifies how it differs from the sibling sprite_list_palettes, which appears to overlap with the 'lists all semantic color roles' claim.

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?

No guidance on when to use this versus sprite_list_palettes, or which parameter combination triggers which of the four described modes. An agent must infer that passing `name` switches palettes and `colors`(+`name`) installs, without any explicit when-to-use or when-not-to-use statement.

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