get_fonts

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

No annotations are provided, so the description bears full responsibility. It states only that it gets font information, without disclosing behavioral traits such as whether it triggers network requests, modifies the page, or has performance implications. Critical details like side effects or dependency on page rendering are missing.

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 short sentence that is efficient and front-loaded. Every word is necessary; there is no wasted space.

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 no parameters and no output schema, the description is minimal. It tells what the tool does but fails to mention the return format or any constraints. For a simple information retrieval tool, this is adequate but not fully complete.

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?

The tool has zero parameters and the schema coverage is 100% (trivially). According to calibration guidelines, the baseline for 0 parameters is 4. The description does not need to add parameter details, and it correctly implies no input is needed.

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 clearly states it retrieves all font information from the page ('获取页面使用的所有字体信息'). It uses a specific verb ('get') and resource ('fonts'), and it distinguishes itself from sibling tools like 'get_element_styles' or 'analyze_layout', which target different aspects.

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 description implies usage when font information is needed, but it provides no explicit guidance about when to use this tool compared to alternatives. It lacks when-not-to-use advice or mentions of prerequisites.

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