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

Annotations already mark this as read-only, which is not contradicted. The description adds value by disclosing that every name is 'grounded in a real archive source' and that the tool offers 'naming styles', giving insight into output quality and behavior beyond the annotation.

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 three sentences, each earning its place: the first states the core action, the second lists style options, and the third reinforces archive grounding and the primary use case. It is front-loaded and free of fluff.

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 an output schema present, return values need not be described. The description covers purpose, styles, archive grounding, and the Shopify context, making it complete for a generation tool. Optional parameters are left to the schema, which is acceptable given high schema coverage.

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%, so the baseline is 3. The description lists style options already present in the schema and adds no extra meaning for parameters like market or n_names beyond what the schema descriptions already provide. It does not compensate with additional parameter details.

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 uses a specific verb ('Generate') with a clear resource ('colour names for any hex value') and differentiates from sibling tools by emphasizing archive-verified grounding and naming styles. It also mentions the Shopify product naming use case, which clarifies the intended domain.

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 usage for Shopify product naming and any hex value, but it does not explicitly state when to use this tool over siblings like ecommerce_namer or colour_hooks, nor does it provide exclusions. The 'core of the Shopify product naming use case' gives some context, but no alternatives are named.

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