zoom_list_recordings

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

With no annotations, the description carries full burden. It discloses the location (~/Documents/Zoom), sorting order (newest first), and listed fields (meeting name, date). It does not mention read-only status or permissions, but the behavior is sufficiently transparent for a simple list operation.

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 single front-loaded sentence, but it is truncated ('dat...'), which suggests incomplete information. While concise, truncation undermines clarity.

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 simple list tool with no input schema or output schema, the description covers the essential behavior (source, sorting, fields) but is truncated and lacks details about potential errors or limitations (e.g., only local files, no search/filtering).

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?

The tool has zero parameters, so the description needs to add no parameter info beyond the schema. It adds value by describing the output content (meeting name, date), which compensates for the lack of 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 lists locally saved Zoom recordings from ~/Documents/Zoom, sorted newest first, including meeting name and date. It uses a specific verb ('Lists') and resource, distinguishing it from the sibling 'zoom_read_transcript' which reads transcript content.

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 use for browsing local recordings but provides no explicit guidance on when to use or not use this tool versus alternatives. No exclusions or context for sibling tools like 'zoom_read_transcript' are provided.

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