Test Fonts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to state whether the tool is read-only or performs mutations, what side effects it may have (e.g., does it crawl pages, take screenshots?), or any operational constraints. The description provides no behavioral transparency beyond the topic list, leaving the agent uninformed about the tool's execution characteristics. There is no contradiction, but the lack of information is a severe gap.

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 a single sentence with no filler, which is concise. However, it is overly brief to the point of under-specification, but conciseness itself is fine. The topic list is front-loaded, but the lack of elaboration means it sacrifices clarity for brevity, yet it earns a 4 for effective brevity without redundant text.

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 the existence of an output schema, the description need not explain return values, but it must explain how to invoke the tool. With 0% schema coverage, the parameters are undocumented, the purpose is vague, and there are no usage guidelines. For a tool with two parameters and no annotations, this is completely inadequate. The description leaves critical information about input semantics and tool behavior undisclosed.

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 the schema provides no descriptions for 'target' or 'max_pages'. The tool description does not compensate by explaining what 'target' refers to (e.g., URL, page?) or how 'max_pages' limits the test. Neither parameter is documented anywhere, making it impossible for an agent to know what values to supply. The description adds no semantic meaning.

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 is a vague list of font-related concerns ('uniformity of families and sizes, unloaded web fonts, heading hierarchy') without a clear verb or explicit statement of what the tool does. It implies testing, but does not say 'tests' or 'checks' directly. It does not distinguish itself from sibling tools like test_layout or test_images, which could overlap in visual testing.

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?

There is no guidance on when to use this tool versus alternatives. The description only lists font issues, but does not explain the context or conditions under which an agent should invoke it (e.g., when checking typography specifically). The sibling names provide some context but are not referenced. No exclusions or alternatives are mentioned.

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