list_zoom_meetings

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

With no annotations, the description carries the full burden. It discloses that the operation targets the authenticated user's meetings, describes the return type as 'dict containing list of meetings,' and adds max/default constraints for page_size. It doesn't explicitly state it's read-only, but the verb 'List' makes that clear, and there are no side effects to disclose.

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 a compact docstring with clear Args/Returns sections. The one-line purpose is front-loaded, and every sentence adds necessary information without redundancy or filler.

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?

For a read-only list tool with two optional parameters and an existing output schema, the description covers key aspects: authentication scope, parameter semantics, and return shape. It doesn't elaborate on pagination behavior beyond page_size, but the output schema likely handles return details, making the description sufficiently complete.

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 0%, so the description fully compensates. It enumerates meeting_type options with parenthetical meanings and states the max/default for page_size, adding constraints not present in the schema. This provides complete parameter semantics beyond the raw JSON 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 uses the specific verb 'List' with the resource 'Zoom meetings' and clarifies the scope to 'the authenticated user.' This clearly differentiates it from sibling tools like get_zoom_meeting (singular fetch) and create_zoom_meeting/delete_zoom_meeting.

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 meeting_type parameter implies usage contexts (scheduled, live, upcoming), but the description never explicitly contrasts with alternatives such as get_zoom_meeting or states when not to use this tool. There are no exclusion guidelines, so it only reaches the 'implied usage' level.

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