palette_apply

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

destructiveHint=true already signals mutation, and "Replaces" is consistent with that. The description adds genuinely useful behavioral scope (which paint carriers are affected, and that global palettes are untouched), but omits the optimistic-concurrency behavior implied by expectedRevision and any scale limit (replacements capped at 128).

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?

One dense, front-loaded sentence that leads with the action and enumerates the affected paint carriers, then closes with the exclusion. No filler sentences; every clause carries information an agent needs.

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?

An output schema exists, so return values need not be described, and the destructive annotation plus the description's scope statement cover the safety profile. For a four-parameter mutation the description supplies the conceptual framing (hex-in/hex-out replacement with local-only scope), leaving only revision semantics to the schema.

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 schema description coverage at 0%, the description has to carry parameter meaning, and it does explain the nature of the mapping (local hex paint "from" -> "to" replacements) that the replacements array encodes. However, it says nothing about expectedRevision (concurrency guard), path, or workspaceId beyond what their names imply, so full compensation is not achieved.

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 ("Replaces") and a precisely bounded resource: local hex paints in attributes, typed inline fill/stroke/stop-color styles, and local CSS variable values. It even delimits scope against the sibling-ish concept of global Inkscape palettes, so an agent can distinguish it from palette_inspect/color_management_inspect, though it never names those siblings.

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 closing clause "without reading global Inkscape palettes" implies this tool is for local/inline color substitution rather than palette-driven recoloring, which is useful orientation. But there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. palette_inspect for global palettes), leaving the routing to inference.

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