timeline_items

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

With no annotations, the description must disclose behavioral traits. It only states it lists clips and index base, but fails to mention if there are side effects (none likely), error handling for invalid indices or track types, or what exactly is returned (e.g., clip names, durations).

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 extremely concise—one sentence plus a clarifying clause—with no redundant words, and the key action is front-loaded.

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?

Given no annotations and no output schema, the description lacks details about parameter defaults, valid values for track_type, what constitutes a 'clip,' and how the tool handles edge cases, making it incomplete for reliable agent invocation.

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 description clarifies that track_index is 1-based, adding value beyond the parameter name. However, with 0% schema description coverage, it does not explain track_type values or that both parameters have defaults, leaving room for ambiguity.

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 clearly states the verb 'List' and resource 'clips on one track of the current timeline', distinguishing it from siblings like timeline_all_items which lists all items across tracks.

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?

It mentions indices are 1-based, which guides usage for the track_index parameter, but lacks explicit guidance on when to use this tool vs alternatives like timeline_all_items or track_info, especially given the large number of sibling tools.

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