zoom_list_recordings

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

No annotations are provided, so the description must disclose behavioral traits. It omits critical details such as pagination behavior, rate limits, required permissions, or data retention policies. The description only states the action and return fields, leaving significant gaps in transparency.

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 sentence that front-loads the core action and then states what is returned. Every word is informative and there is no redundancy.

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 has 5 parameters (including pagination) and no output schema, the description should explain return format, pagination mechanics, and error conditions. It does not address these, leaving an agent without sufficient context for correct 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?

The input schema has 100% description coverage, so the schema already documents each parameter. The description adds no new meaning to the parameters (e.g., does not clarify that 'from' and 'to' are required for date range or explain the meaning of 'page_size' beyond the schema). It adds value only by linking the output to transcripts.

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 'List' and the resource 'cloud recordings for a Zoom user within a date range', and specifies return values (meeting topics, dates, recording IDs) needed for transcripts. This distinguishes it from sibling tools like zoom_list_meetings and zoom_get_meeting_transcript.

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 when needing recording IDs for fetching transcripts, providing context for a workflow. However, it does not explicitly state when to use this tool versus alternatives (e.g., for local recordings or other listing tools) or mention prerequisites like authentication.

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