get_caption_tracks

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

No annotations are provided, so the description carries the full burden; it makes clear this is a read operation scoped to the active sequence, which is the key behavioral fact. It says nothing about what happens when no sequence is active, whether results are paginated, or what the return structure looks like, and there is no output schema to compensate.

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 short sentence with zero filler, and the resource and scope are front-loaded. Nothing could be trimmed without losing information.

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 zero-param getter with no output schema and no annotations, the description is only minimally sufficient: it identifies the resource and scope but not what a caption track record contains or how the caller should proceed if the active sequence is empty. The missing return-shape detail matters more here precisely because no output schema exists.

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?

The tool takes zero parameters, so the schema is trivially complete and the description has no parameter semantics to add. Baseline of 4 applies; no gaps exist because nothing is accepted as input.

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 (get caption/subtitle tracks) plus a scope (active sequence), which is more than a restatement of the name. It does not, however, distinguish itself from the nearby get_captions or add_caption_track siblings, so an agent must infer that 'tracks' means the containers rather than the caption clips inside them.

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 phrase 'on the active sequence' hints that an active sequence must exist, but there is no explicit when-to-use, no exclusion, and no pointer to get_captions as the alternative for reading individual captions. The agent is left to infer routing from the name alone.

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