list_jobs

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 by structured data. The description adds two real behavioral facts — results are paginated one page at a time and are scoped to the connected account — but says nothing about ordering, cursor lifetime, or whether listing includes completed/failed jobs.

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, front-loaded with the core action and the mode distinction, with no filler. The trailing sentence about account scope is brief and purposeful, though slightly vague.

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 and 0% schema description coverage, the definition should describe what a returned job record contains (status, type, timing) and how cursor pages terminate. It covers the action and scope but leaves the return payload opaque.

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 implies bulkJobId selects a progress read, but never names 'cursor' or explains that it advances pagination, leaving one of two parameters unexplained in both schema and prose.

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 gives a specific verb ('List') plus resource ('batch/channel jobs') and distinguishes two modes: paging through jobs vs. reading progress for a specific bulkJobId. It is clear what the tool does, though it does not name any sibling by contrast.

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?

Usage is only implied: the presence of bulkJobId suggests a targeted progress read, while omitting it implies listing a page. There is no explicit 'use this when... use X instead' guidance and no mention of how it relates to siblings such as transcribe_bulk or get_transcription.

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