generate_typography_system

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns CSS custom properties, Tailwind config, or Google Fonts embed HTML, and mentions format options. However, it does not disclose any side effects, state changes, or constraints 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 very concise, with two sentences that front-load the purpose and efficiently add key details about return formats. Every sentence adds value without waste.

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 7 parameters, 1 required, no annotations, and an existing output schema, the description is adequate but incomplete. It covers the general purpose and output formats, but omits details on parameter usage, valid scale values, or font specification, leaving gaps for a tool of this 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 description coverage is 0%, meaning parameter details are absent. The description adds minimal meaning: it mentions 'font selection + scale' and lists format options. It does not explain parameters like heading, body, weights, or base, failing to compensate for the lack of schema 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?

The description clearly states that the tool generates a complete typography system from font selection and scale, and lists output formats. It distinguishes itself well from sibling tools like list_pairings, list_scales, lookup_font, and search_fonts.

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 when a typography system is needed based on font choices and scale, but provides no explicit guidance on when to use or not use this tool versus alternatives, nor any prerequisites or exclusions.

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