Suggest Typography Pairing

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral detail: it returns Google Fonts import links, CSS font-family declarations, recommended weights, and usage notes, and offers markdown/json response formats. No contradiction.

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 well-structured with a summary, Args, Returns, and Examples sections, and the key purpose is front-loaded. However, the Args section largely duplicates the schema's parameter descriptions, adding minor redundancy. Still, it remains compact and scannable.

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?

No output schema exists, but the Returns section explicitly describes the output fields (display font, body font, Google Fonts link, CSS snippet, usage notes). All parameters, defaults, and format options are documented, and examples reinforce usage. For a simple recommendation tool, this is complete.

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 100% coverage with enums and defaults for all 3 parameters, so the baseline is 3. The description's Args section repeats schema values, but the examples ('Get a tech-focused serif+sans mix: style="tech", category="mixed"') clarify how style and category combine, adding meaning beyond the schema.

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 opens with 'Suggest a curated font pairing (display + body font) based on a design style' — a specific verb and resource. This clearly distinguishes it from the sibling ui_generate_type_scale, which handles type scale rather than pairing.

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 frames the tool as a suggestion service for font pairings and lists input options (style, category, response_format) with defaults. It does not explicitly name alternatives or when-not-to-use, but the sibling set (color palette, type scale, spacing) makes the use case evident. Thus context is clear but exclusions are absent.

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