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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false). The description adds useful behavior beyond that: results are ordered 'newest first' and scoped to clips the workflow can already read. It doesn't mention pagination or the limit ceiling, but the ordering and scoping context is genuine added value.

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?

Three tight sentences, front-loaded with what the tool returns, then when to call it, then how to use the result. Zero filler and no repetition of schema content.

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 exists, so return values need not be explained, and annotations carry the safety profile. The description covers the call trigger and downstream usage well; the only mild gap is not naming the complementary upload sibling for routing.

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 workflow_id and limit are already fully documented in the schema. The description adds no parameter-level syntax or format detail, so the baseline 3 applies even though it contextualizes why the tool is called.

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 (audio clips a workflow can already read) with ordering ('newest first'). This clearly distinguishes it from upload_audio_file, finish_audio_upload, and list_script_files among its siblings.

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?

Gives a concrete trigger: call it after the user uploads in the browser to learn the upload_id, and explicitly warns never to guess one. It also explains the downstream step (pass upload_id as audio_upload_id). However, it does not name alternate tools such as upload_audio_file/finish_audio_upload as the complementary actions, leaving some routing to inference.

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