get_font

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

The description goes beyond the readOnlyHint annotation by disclosing the full scope of returned metadata, including variable axes, unicode ranges, license, package names, and CDN URL templates. It is clearly a read operation and no contradictory behavior is stated.

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 with no filler: the first lists the return contents, the second gives essential usage sequencing. The most actionable guidance is front-loaded and every clause earns its place.

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?

For a single-parameter read-only tool, the description fully covers what the agent needs: how to get the id, what metadata will be returned, and when to call this tool relative to siblings. No output schema is needed since the return contents are enumerated directly.

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% and the id parameter description is already rich, with examples, a source instruction, and a warning that it is not the display name. The tool description itself adds no parameter-specific meaning, so the baseline of 3 applies.

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?

States a specific verb and resource: retrieving metadata for one font, and enumerates the exact fields returned. It clearly distinguishes itself from sibling tools by positioning get_font as the metadata lookup before get_font_css or download_font.

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 tells the agent when to call it: before get_font_css or download_font, to learn which subsets and weights exist. This provides concrete sequencing guidance and names the downstream tools it supports.

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