download_transcript

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

No annotations are provided, so the description carries the full burden. It states the action is a download to local storage, implying a read operation, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, what format the download is in (e.g., text file, PDF), or if it overwrites existing local files. The description adds minimal context beyond the basic action.

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, efficient sentence that front-loads the key information: action, resource, and destination. There's no wasted text, and it's appropriately sized for a simple tool with one parameter.

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 no annotations, no output schema, and a simple input schema, the description is adequate but incomplete. It covers the purpose and destination but lacks details on behavioral aspects (e.g., file format, permissions) and output (e.g., success/failure indicators), which are important for a download operation. It's minimally viable but has clear gaps.

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, with the 'meetingId' parameter documented as 'Zoom meeting ID or UUID'. The description doesn't add any further meaning about parameters, such as examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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 specific action ('download'), target resource ('Zoom meeting transcript'), and destination ('from the cloud to local storage'). It distinguishes from siblings like 'check_local_transcripts' (which checks local storage) and 'get_recent_transcripts' (which likely lists rather than downloads).

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 a transcript needs to be downloaded to local storage, but it doesn't explicitly state when to use this tool versus alternatives like 'check_local_transcripts' (for local availability) or 'search_transcripts' (for finding transcripts without downloading). No exclusions or prerequisites are mentioned.

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