List transcripts

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

With readOnlyHint=true annotation, the safety profile is already covered. The description adds that the tool returns metadata (not full content) and supports filtering, which is useful. However, it does not disclose behaviors such as pagination, ordering, or how the limit parameter behaves beyond the schema. No contradiction with annotations.

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, concise sentence that conveys the core purpose and filtering capability without unnecessary words. It is well-structured and easy to parse.

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 simple read-only list operation, the description is adequate: it indicates the return type (metadata) and filter options. It does not detail pagination or the exact shape of returned metadata, but given the simple nature and lack of output schema, the description provides sufficient context for use.

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% (tag and participant have descriptions, limit lacks one). The description reinforces the role of tag and participant as filters but does not mention limit. It adds a high-level framing but does not significantly enhance the schema's own parameter descriptions.

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 action ('List') and resource ('transcript metadata'), distinguishing it from siblings: get_transcript likely retrieves a single full transcript, and search_transcripts implies broader search. The optional filter phrase adds specificity without ambiguity.

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 for browsing metadata with optional filters, but it does not explicitly state when to prefer this over search_transcripts or get_transcript, nor does it provide exclusions or alternative recommendations. The sibling names offer context, but the description itself lacks direct usage guidance.

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