Inspect or Install Google Font

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

No annotations are provided, so this description carries the full load and does reasonably well: it discloses that install writes local files, that content hashing and signature checking are applied, that an overwrite safeguard exists, and that licensing/glyph coverage are the user's responsibility. It omits return shape and failure behavior, which keeps it below 5.

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 compact clauses; the read-vs-write distinction is front-loaded and the caveat is placed last as a closing warning. Dense but no wasted sentences.

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?

With no annotations and no output schema, the description should say more about what 'face metadata' actually contains and what happens on a hash/signature mismatch. The safety story is covered, but the inspection result is left opaque.

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?

At 67% schema coverage, the description adds meaning for the install/weights/overwrite path ('selected font weights', 'content hash, signature and overwrite safeguards'). But it never mentions the `style` parameter (an undocumented enum) or the `dir` default, so it doesn't fully compensate for the coverage gap.

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+resource ('Fetch Google Fonts CSS2 WOFF2 face metadata') plus the optional mutation ('install selected font weights'). The two modes are clearly distinguished, though nothing separates it from siblings (none of which are font tools, so the cost is low).

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 word 'optionally' implies inspect-by-default and install-on-demand, but the description never states when to pick one mode over the other or any prerequisites (e.g., project must have a public/ dir). The warning 'License and glyph coverage require review' hints at a precondition without spelling it out.

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