search_fonts

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

No annotations provided; description only covers modes and tier filter without disclosing output format, pagination, or any other behavioral aspects like read-only nature.

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?

Extremely concise with clear bullet points for modes; every sentence adds value.

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?

Output schema exists but not described; missing explanation for query and max_results; sibling tools exist but description doesn't explicitly contrast.

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%. Description adds meaning for mode (options) and tier (applies to single mode only), but does not explain query or max_results parameters.

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 'Search Google Fonts by description, mood, or use case' and details modes, clearly distinguishing from siblings like lookup_font (specific lookup) and list_pairings/list_scales (pre-defined sets).

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?

Describes modes and tier filter constraints, giving context on when to use each mode, but does not explicitly state when not to use or provide alternatives.

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