list_asset_subtitles

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

No annotations are provided, so the description carries the full disclosure burden. It only says 'List all subtitle tracks' and does not mention response shape, whether subtitle metadata includes language or format fields, or how version_id changes the result set. This is minimal for a tool with no annotation safety hints.

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 sentence with no filler, front-loading the verb and resource immediately. It earns its place, though it could be expanded with minimal effort to improve usefulness.

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 straightforward list operation with a clear required parameter, the description is minimally viable. However, with no output schema and no mention of return contents or behavior relative to version_id, an agent may not know what data to expect from the response.

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 100%; both asset_id and version_id are already documented in the schema. The tool description adds no further parameter context beyond the resource-level 'subtitle tracks for an asset', so baseline 3 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?

The description states a specific verb ('List') and resource ('all subtitle tracks for an asset'), making it clear what the tool returns. It does not explicitly contrast with siblings like get_subtitle_webvtt or export_segments_srt, but the 'list' framing implies metadata coverage rather than content retrieval.

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 gives no guidance on when to use this tool instead of related siblings such as list_asset_segments, get_subtitle_webvtt, or get_transcription_subtitles. An agent must infer the intended selection from the tool name alone.

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