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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context on top: the response is paged and must be re-fetched with next_offset until null, and each format changes the shape of what comes back. It stops short of noting error behavior or rate limits, so not a 5.

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?

Three compact sentences cover format semantics, paging, and endpoint with no filler. The opening fragment 'The transcript of a transcribed job.' is slightly circular, but the rest is front-loaded and information-dense.

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?

With no output schema, the description carries the return-value burden and does so for both formats plus pagination. group_channels_by is left to the schema (which documents it as multichannel-only), and the non-applicability of that parameter in the description is a minor gap.

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 coverage is 100%, so the baseline would be 3, but the description goes further by explaining that format=segments returns {speaker, start, end, text} per turn in seconds and that text includes speaker labels and timestamps, and by tying offset/next_offset to the paging loop. That is meaning the schema alone does not convey.

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?

States the resource (the transcript of a job) and the underlying endpoint GET /jobs/{id}/transcript, and spells out the two output formats. It does not differentiate itself from siblings such as revai_get_captions or revai_get_summary, so an agent must infer which of the three 'retrieve artifact' tools applies.

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?

Paging guidance ('repeat with next_offset until it is null') and the default of format=text give implied operating instructions, but there is no explicit when-to-use vs when-not-to-use, and no routing against revai_get_captions/revai_get_summary. Usage is inferable rather than stated.

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