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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context by disclosing that results are a bounded (paginated) page scoped to the connected tenant, though it says nothing about cursor lifetime, ordering, or what happens when the page is exhausted.

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?

A single front-loaded sentence that names the resource, the pagination trait, and the filter surface with no filler. Every clause carries information.

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?

An output schema and complete annotations reduce what the description must do, and the enumeration semantics are conveyed. Gaps remain around pagination usage (cursor/pageSize behavior) and the distinction from search_library, which matters in a sibling set this large.

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 0%, so the description carries the burden, and it covers three of five parameters (status, folderId via 'folder', includeDeleted via 'deleted state'). It says nothing about cursor or pageSize, leaving the two pagination parameters defined only by their types and constraints.

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 ('Lists a bounded page of transcripts') plus the tenant scope and the three filter dimensions, which clearly separates it from single-item siblings like get_transcript. It never names search_library, so the boundary against fuzzy search must be inferred.

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 mention of status/folder/deleted filtering implies the browsing-and-filtering use case, but there is no explicit when-to-use and no reference to alternatives such as search_library or list_folders. An agent must infer that this is the enumeration path rather than the search path.

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