Server Quality Checklist

Tool Scores

• fathom_list_meetingsA
  3.6/5.0
  Behavior3/5

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

  Description indicates read-only operation (list), and discloses return fields. No annotations provided, so description carries burden but lacks details on authentication, rate limits, or pagination behavior beyond what schema provides. Adequate but not rich.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Single sentence, front-loaded with action and resource, no wasted words. Could slightly expand on output structure but remains efficient.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  4 params, no required, no output schema. Description lists return fields but not structure (e.g., array of objects), and omits pagination details. Adequate for a list tool but missing some completeness.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, so baseline is 3. Description adds 'with optional date filters' but no parameter-specific details beyond schema. No added value over what schema already provided.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Description uses specific verb 'List' and resource 'meetings from Fathom' with optional date filters, clearly distinguishing from sibling tools that search or retrieve individual meetings.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Implied usage for listing recent/date-filtered meetings, but no explicit guidance on when to use vs siblings (e.g., search_meetings for keyword search). No when-not-to-use or alternative suggestions.

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

• fathom_get_transcriptA
  3.8/5.0
  Behavior3/5

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

  No annotations provided; description mentions large size but does not disclose other behavioral traits such as read-only nature, latency, or output format beyond basic structure.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two sentences, no fluff. Front-loaded with purpose, followed by usage guidance. Every sentence earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Adequate for a simple one-parameter tool with no output schema. It explains what the tool returns and gives usage advice, though it could specify output format more precisely.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description covers the only parameter (recording_id) fully. The tool description adds no additional meaning beyond restating the parameter name.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Clearly states it retrieves a full transcript with speaker labels and timestamps. Does not explicitly differentiate from fathom_get_summary or fathom_search_meetings, only from fathom_list_meetings.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Provides explicit advice to use sparingly due to size and suggests an alternative for quick overviews (fathom_list_meetings). Does not address when to use other siblings like fathom_get_summary.

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

• fathom_get_summaryA
  3.9/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries full burden. It mentions 'returns markdown-formatted summary' which hints at read-only behavior, but does not state side effects, auth requirements, or rate limits. Adequate but could be more explicit.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two short, direct sentences with no redundant information. Front-loaded with purpose and output format.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple retrieval tool with one required parameter and no output schema, the description is complete: it specifies input source, output format, and core functionality.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100% for the single parameter, which already explains it comes from fathom_list_meetings. The tool description adds no additional semantic information beyond what the schema provides.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Description clearly states the tool gets an AI-generated summary for a specific meeting, explicitly mentioning the markdown format. It is distinct from siblings like fathom_get_transcript (different output) and fathom_list_meetings (different purpose).

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No explicit guidance on when to use this tool vs alternatives. It is implied that one uses it when needing a summary rather than a transcript, but there are no when-not or alternative recommendations.

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

• fathom_search_meetingsA
  4.1/5.0
  Behavior3/5

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

  Reveals that the tool only searches the most recent 50 meetings and performs client-side filtering. Annotations are absent, so the description provides the primary behavioral context. Missing details on case sensitivity, exact matching, or behavior when query matches more than 50 meetings.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Three sentences, each essential: purpose, technical limitation, and usage tip. Concise and front-loaded with no wasted words.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Covers input behavior well but lacks details on output format, pagination, or how results are returned. Without an output schema, the description should clarify what the tool returns (e.g., meeting IDs, metadata).

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  All parameters have schema descriptions (100% coverage). The description adds value by explaining the client-side filtering context and how the 'after' parameter narrows the window, enhancing understanding beyond the schema.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the verb ('Search'), resource ('meetings'), and scope ('most recent 50 by keyword in title'). It distinguishes from sibling tools like fathom_list_meetings, which lists all meetings without keyword filtering.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Explains that client-side filtering is used due to API limitations, and advises using the 'after' param to narrow the search window. However, it does not explicitly compare to sibling tools or state when not to use this tool.

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