font_validate

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

Discloses that it reports errors, warnings, and observations, but does not clarify side effects such as whether a compiled TTF artifact is persisted; annotations are all false and add no clarity.

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 concise sentences with no redundant phrasing; the structure is clear and easy to parse.

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?

An output schema is present so return values need not be described, but the lack of parameter semantics and explicit usage guidance leaves the tool partially under-specified.

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?

No parameter descriptions are provided; corpus and revision semantics are unexplained, and the schema has 0% description coverage.

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 action ('Run technical checks, compile a TTF, inspect tables and corpus coverage') and clearly distinguishes the tool by noting it does not assess artistic merit.

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?

Implies a validation-focused use case and explicitly excludes artistic assessment, but does not clearly indicate when to use this over sibling tools like font_build or project_inspect.

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