fathom_list_meetings

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.

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.

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.

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.

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.

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.