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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond annotations: results are ordered newest-first, and transcript text is deliberately excluded (status, duration, language only), which tells an agent it must call get_transcription for actual content.

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 zero waste. Ordering, returned fields, and the exclusion of transcript text are all packed into compact phrases.

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 usefully enumerates returned fields (status, duration, language) and discloses ordering and the transcript-text exclusion. The main gap is pagination behavior and default limit, which leave an agent guessing how to page through results.

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 must carry parameter meaning. It only addresses the 'status' filter; limit and offset (pagination) are undocumented, and 'newest first' does not explain how offset interacts with ordering. Two of three parameters are left unexplained.

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 ('Your transcriptions') with a precise scope, and the parenthetical clarifies what fields are included. It does not explicitly distinguish itself from siblings like get_transcription or transcribe_media, so it stops short of a 5.

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 status' hints at an intended usage pattern, and 'newest first' implies a browsing scenario. However, there is no explicit when-to-use guidance, no naming of the single-item sibling get_transcription, and no guidance on when filtering is warranted.

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