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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that results cover both call and voicemail transcripts, which is useful scoping context, but says nothing about pagination behavior or result ordering beyond what the schema's next/limit fields imply.

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?

Two short sentences with the resource up front and the filtering note second. No filler, though it's terse enough that it leaves gaps rather than being optimally structured.

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 6 optional params, no output schema, and no annotations beyond readOnlyHint, the description is minimally adequate. It doesn't clarify what a transcript object contains or how sourceContextId aligns with sourceId, leaving a gap an agent would have to guess at.

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 67%, with since/before/limit/next well documented in the schema. The description only loosely maps 'time window' and 'source' to those params and adds nothing for sourceContextId or the millisecond-timestamp format, so it's baseline-equivalent to the schema rather than additive.

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 a specific verb and resource ('List call and voicemail transcripts'), which distinguishes it from the singular get_transcript and get_transcript_segments siblings. It doesn't explicitly name those siblings, but the plural/list framing makes the distinction inferable.

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?

'Filter by time window or source' hints at when the filters are useful but gives no explicit when-to-use vs. when-to-call-get_transcript guidance. The alternative and its selection condition are left implicit.

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