find_fontsSearch installed fonts by family, style, or PostScript name to retrieve PostScript names for set_text in After Effects 24.0+.
Search the installed fonts by family, style or PostScript name (e.g. "montserrat", "bold italic"); returns PostScript names for set_text font. Needs After Effects 24.0+.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Words that must all match (default: list every font) |
Changes observed during successful MCP inspections.
v2.22.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuine value beyond them: the return format (PostScript names) and a version gate (After Effects 24.0+).
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 tight clauses with the purpose front-loaded, then the requirement note. No filler and nothing redundant with the schema.
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?
No output schema exists, and the description supplies the essential return-value context (PostScript names) plus the version prerequisite. The only shortfall is silence on the limit parameter's behavior.
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 coverage is 50%. The description usefully explains that the query matches against family, style, or PostScript name with examples, supplementing the schema's 'Words that must all match'. However, the limit parameter remains undocumented in both schema and description, so it does not fully compensate for the 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 (search) and resource (installed fonts) plus the three searchable fields (family, style, PostScript name) with examples. It does not explicitly differentiate from the parallel find_effects sibling, though the pointer to set_text clarifies its role.
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?
Gives clear usage context by naming the consumer tool ('returns PostScript names for set_text font') and a prerequisite ('Needs After Effects 24.0+'). It lacks explicit when-not-to-use guidance or a named alternative, keeping it below a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.