list_meetings

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context: the meetings are scoped to the authenticated user, pagination is available, and certain fields are optional includes. However, it does not mention authentication requirements, rate limits, default pagination size, or potential errors. Since this is a read-only list operation, the lack of side-effect disclosure is less critical, but the description still leaves significant behavioral aspects unspecified.

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?

The description is two sentences, front-loaded with the core purpose and followed by a concise summary of capabilities. Every sentence earns its place with no fluff or redundancy. It is appropriately sized for a tool with 12 parameters, giving a high-level overview without excessive detail.

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?

Given the tool's complexity (12 parameters, output schema, multiple optional includes), the description provides a solid overview: it states the scope (user's meetings), lists the main filter dimensions, mentions pagination, and notes optional enrichments. The output schema further covers return values, so the description does not need to detail them. It lacks some specifics like default ordering or pagination limits, but these are less critical for an initial invocation. Overall, it is sufficiently complete for an agent to understand the tool's role and basic usage.

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 58%, leaving several parameters (cursor, include_* booleans) without individual descriptions. The tool description compensates by explaining that cursor is for pagination and that the boolean flags control optional includes (action items, CRM matches, summaries, transcripts). It also groups filter types (participants, date ranges, recording users, teams), adding semantic structure beyond the raw schema. This meaningfully helps an agent understand how to use the 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?

The description clearly states the tool's function with a specific verb ('List') and resource ('meetings'), and adds an important scope qualifier ('recorded by or shared with the authenticated user'). This distinguishes it from sibling tools like get_summary and get_transcript, which fetch specific artifacts, and list_teams/list_team_members, which list other resources.

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?

The description implies usage by describing capabilities (pagination, filters, optional includes), but does not explicitly state when to prefer this tool over alternatives. For example, it mentions optional includes for summaries and transcripts, which suggests it could replace get_summary/get_transcript in some cases, but it does not give explicit guidance on when to use those tools instead. The usage is implied but not articulated.

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