fathom_search_meetings

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.

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.

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.

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.

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.

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.