assemblyai_list_transcripts

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds two useful hints beyond that: results are 'recent' (implying a recency bound or default window) and scoped to 'the account' (implying API-key account scoping). It does not mention pagination or result ordering, which is a gap for a list tool.

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 with no wasted words. It is efficient, though the 'recent' qualifier is left unexplained rather than elaborated.

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 read-only list tool with full schema coverage and annotations, this is nearly complete. The only missing piece is clarification of what 'recent' means (default window, pagination behavior via cursors), which the schema hints at but does not tie back to the description.

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 limit, status, api_key and both cursors are fully documented in the schema. The description adds no parameter-level detail, so the baseline 3 for high-coverage schemas is appropriate.

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 (List) and resource (AssemblyAI transcripts) scoped to the account, with the qualifier 'recent' indicating a bounded result set. It is reasonably distinguishable from assemblyai_get_transcript (singular fetch) by virtue of being a plural list, but does not explicitly name that sibling.

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 offers no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer that this is the discovery step preceding get_transcript/get_sentences, which is not stated anywhere in the text.

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