Assign Color Profile

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond them by clarifying the effect is tag-only with no ICC conversion, plus a note on background execution. It still doesn't explain why the op is destructive or whether the change is reversible.

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 action is front-loaded, followed by a clearly-marked warning and the alternative, so an agent reading only the first sentence grasps the tool. The closing note about not invoking Computer Use is slightly meta but does not bury the key content.

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 single-parameter mutation with no output schema, the description supplies purpose, the key caveat, and the alternative. It is largely complete; the only minor gap is the absence of any note on reversibility or required context, which the destructiveHint hints at but does not explain.

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 100% and the single 'profile' parameter is documented as 'Color profile name or path'. The description adds no syntax, format, or naming detail beyond the schema, so the baseline 3 is appropriate.

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+resource ('Assign (tag) a color profile to the document') and immediately disambiguates it from the similarly-named conversion operation. An agent can tell it apart from siblings like replace_color or manage_swatches 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?

Clearly states the boundary of the tool ('only changes the profile tag — it does NOT convert color values') and points to the alternative for full conversion. However, the alternative named is an Illustrator UI path rather than a sibling MCP tool, so routing among the listed tools is not fully resolved.

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