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

Annotations declare destructive/irreversible and idempotent, but the description goes well beyond them: it explains that grayscale permanently discards color, that grayscale-to-rgb does not restore it, that indexed sources are refused, that live filters block conversion, and that the no-op check precedes the refusal. This is unusually rich behavioral disclosure for a destructive mutation 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 core purpose is front-loaded in the first clause, with constraints and alternatives following in a logical order. It is dense and parenthetical-heavy, but nearly every clause carries actionable information, so the length is largely earned.

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?

With annotations covering the safety profile and an output schema covering the return shape, the description supplies everything an agent needs: refusal conditions, irreversible effects, ordering of the no-op check, and remediation paths. Nothing material is missing.

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 both parameters are already documented; the enum on mode and the image id note carry the structured meaning. The description reinforces the indexed-source refusal and conversion direction but adds little syntax or format detail beyond the schema, so the 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 and resource (convert the photo's base color mode) with explicit directionality (rgb <-> grayscale) and scoping (indexed refused as source). An agent can distinguish this from siblings like recolor, apply_look, or manage_filters without opening any schema.

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?

Gives explicit preconditions and routing: bake or manage_filters op=delete the live filter first, or the call REFUSES; a checkpoint is recommended when in doubt. It also clarifies ordering around the no-op case, so the agent knows exactly when a call will succeed, fail, or be a no-op.

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