replace_color

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the mutation (replacement) and scope but omits crucial details such as how tolerance affects matching, whether changes are destructive/reversible, and what response to expect. This is inadequate for a tool that modifies sprite data.

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 a single, well-structured sentence that front-loads the action and immediately clarifies scope. Every word earned its place with no redundancy.

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 5 parameters, no annotations, and no output schema, a one-sentence description is insufficient. It lacks explanation of tolerance behavior, side effects, return values, or default behavior when layer/frame are omitted (though the scope mention partially covers this). The description feels under-specified compared to the tool's complexity.

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?

The schema leaves 'frame' and 'layer' undocumented (0 out of 5 params have descriptions, but the description compensates by explicitly mentioning 'layer/frame' as scope targets). It adds meaning for these otherwise unspecified parameters. For 'from_color', 'to_color', and 'tolerance', the schema already provides descriptions, so the description does not need to repeat them.

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 function: 'Replace one color with another' with explicit scope options ('entire sprite or a layer/frame'). This specific verb+resource+scope distinguishes it from all sibling tools, none of which perform color replacement.

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 provides clear context on usage by specifying the tool can act on the entire sprite or a specific layer/frame. It does not explicitly mention alternatives, but since no sibling tool offers comparable functionality, this is not a significant omission.

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