zoom_read_transcript

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

No annotations provided. The truncated description lacks disclosure of behavioral traits such as file location requirements, format specifics, or error conditions. Carries the full burden but fails to deliver.

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 truncated sentence. It is not appropriately sized; the truncation indicates poor structure and incompleteness.

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?

No output schema, no annotations, and a truncated description. The tool's complexity is low, but the description fails to provide complete context about return values or operation details.

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?

With zero parameters, the description does not need to add parameter meaning. Schema coverage is 100% trivially, so baseline is appropriate at 4.

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 indicates it reads transcript/captions from a local Zoom recording, but is truncated, leaving ambiguity about the exact artifacts. It is a specific verb+resource but incomplete, reducing clarity.

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?

No guidance on when to use this tool versus alternatives like zoom_list_recordings. The description does not provide context for appropriate use or prerequisites.

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