designer_get_font_pairing

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

No annotations provided, but description details return content: heading+body+mono fonts with weights, tracking, line-height, Google Fonts import, rationale. No contradictions. Lacks explicit read-only statement but sufficiently transparent.

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: first states purpose and filters, second lists return details. No fluff, front-loaded.

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, but description fully covers return fields, data types, and rationale. Parameter usage clear. Complete for tool complexity.

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 covers 100% with enums and descriptions. Description adds '21 pairings available' and implies combinable filters. Provides extra context beyond 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?

Description clearly states 'Get curated font pairings' with specific filters (mood, industry). Distinguishes from sibling tools like designer_get_personality by focusing on font pairing output.

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?

Explicitly says filtered by mood and/or industry, with 21 pairings available. Implies use when needing font choices, but no explicit when-not or alternatives provided.

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