generate_harmony

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

No annotations are provided, so the description must bear full responsibility for behavioral disclosure. It mentions that the tool returns a list of hex colors but does not address side effects, idempotency, authentication needs, or any limitations such as rate limits or destructive actions.

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 concise at two sentences, with the first sentence clearly stating the tool's purpose and the second detailing parameter specifications. Every sentence adds value, and there is no superfluous 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?

Given the tool's moderate complexity (two required parameters, no enums in schema but description provides enums), the description covers input formats and output type adequately. It omits error handling or edge cases, but for a generation tool this is acceptable. The output schema exists, so return values are implied.

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 input schema has 0% description coverage, leaving the description to explain parameter semantics. It effectively clarifies that 'base' accepts hex, CSS name, brand name, or saved-palette reference, and enumerates the valid 'scheme' options. However, it could provide examples for the saved-palette reference format.

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 generates a color harmony from a base color, specifying that it accepts various color formats and lists the available scheme types. This specific verb+resource combination distinguishes it from sibling tools like convert_color or contrast_check.

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 implies use for generating harmony schemes but does not explicitly state when to use this tool versus alternatives like get_palette or list_palettes. No exclusion criteria or alternative suggestions are provided.

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