add_colors

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

No annotations are provided, so the description must carry the burden. It details valid fields and clarifies the absence of a usage field, which is helpful. However, it does not mention the max 50 limit (present in schema) or whether swatches are appended or replaced.

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?

Two sentences, no filler. The first sentence states the primary action, the second provides critical field details and a caution. Every word earns its place.

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?

Given no annotations or output schema, the description covers the essential aspects: what it does, field requirements, and a notable exclusion. It could mention the maximum number of swatches (though in schema) or behavior on existing swatches, but overall it is sufficient.

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%, but the description adds value by providing examples and clarifying the format for rgb, cmyk, and pantone. It also explicitly states that hex is required in #rrggbb format, enhancing the schema's descriptions.

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?

Description clearly states the action 'Add color swatches to a Colors block'. It uses a specific verb and resource, making the purpose unambiguous. The purpose is distinct from sibling tools like add_typography or set_block_note.

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?

Provides explicit guidance that there is no 'usage' field and directs to set_block_note for usage guidance. This prevents misuse, though it does not elaborate on when to use this tool versus other add tools.

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