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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds that the family name must be exact and sourced from fonts.google.com, which is real behavioral context, but it omits what happens on a misspelled or unavailable family, whether the font is cached or fetched per call, and whether the download is scoped to the project.

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?

A single sentence with the action front-loaded and the input constraint attached directly to the resource. No filler, no restatement of the title, and the payoff clause is compact.

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 three-parameter mutation tool with annotations and no output schema, the description covers what the tool does and how to specify the critical input. It leaves unresolved whether the font becomes available globally or only within the projectId project, and what an invalid family name produces, both of which matter for correct invocation.

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 67%: 'weights' and 'projectId' are self-documented, while 'family' has no schema description at all. The description compensates for exactly that gap by requiring an exact name from fonts.google.com, which is the single most error-prone input. It stops short of explaining weight-list semantics or the default project resolution beyond what the schema already says.

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 ('Download') and resource ('a Google Fonts family'), and the parenthetical '(exact name from fonts.google.com)' pins down the identifier source. It implicitly separates itself from create_font_upload and list_fonts, though it never names those siblings, so the distinction must be inferred.

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 trailing clause 'so captions, text and overlays can use it' gives a use context, implying this is the prerequisite step before styling text. However, there is no explicit when-not guidance and no mention of the natural alternatives (list_fonts to see what is available, create_font_upload for non-Google fonts, remove_font to undo).

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