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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavioral fact — unnamed colors are auto-named to the closest color name — but omits the 24-color cap, default format/value behavior, and what the output looks like.

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?

A single dense sentence front-loaded with the action and an efficient enumeration of formats. No waste, though the long comma list slightly reduces scannability.

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?

A 3-parameter export tool with no output schema, so the description should clarify what gets returned (file contents? string?) and format-specific behavior. It covers formats and auto-naming but leaves the return shape and default values (css/oklch) unexplained.

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 only 33%: the color field is well documented but format, values, and the name field lack in-schema descriptions. The description compensates weakly by listing formats (css, tailwind, scss, json, dtcg, array, svg), but does not explain the 'values' enum or the name field's role, leaving gaps at this coverage level.

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 (export/turn into) and resource (colors to code) plus an exhaustive list of output formats. Clearly distinguishes itself from siblings like generate_palette, convert_color, nearest_names; the agent knows this produces code artifacts, not analyses or generated color sets.

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?

Usage is implied by naming the output formats, but the description never states when to pick this over nearest_names (for naming) or convert_color (for single conversions). No exclusions or alternative guidance, so the agent must infer from format names alone.

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