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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds behavioral context beyond this by specifying that it cleans transcripts to readable lines, reads from local recordings, and includes both transcript and chat. It does not contradict the annotations and provides useful details about output processing.

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 long and front-loaded with the core function. It avoids redundancy and every clause adds value: the first sentence defines what is read and the output format, while the second gives input source and use cases. No wasted words.

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 tool with full parameter schema, an output schema, and clear annotations, the description covers all necessary context: what artifacts are read, how the transcript is cleaned, where to get the input, and typical use cases. It is complete for an agent to select and invoke the tool correctly.

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 100%, so both parameters are already fully documented. The description reinforces the 'recording' parameter by referencing zoom_list_recordings but does not add new semantic details about the 'include' parameter or the recording path format. Baseline 3 applies because the schema carries the burden.

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 a specific verb ('Reads') and resource ('text artifacts of a local Zoom recording'), enumerating the exact artifacts (transcript/captions and chat) and the cleaned output format ('Speaker: text' lines). This clearly distinguishes it from sibling tools like zoom_list_recordings, which lists recordings rather than reading their 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 explicitly tells users to pass the recording name or path from zoom_list_recordings, establishing a clear prerequisite and context for use. It also gives example use cases ('summarize my last meeting'). However, it does not explicitly state when not to use the tool or mention alternatives.

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