list_track_items

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

Annotations already declare `readOnlyHint: true` and `openWorldHint: false`, so the safety profile is covered. The description adds that results include timeline and source ranges, which is useful, but it does not disclose ordering, pagination, or default project/sequence behavior.

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 compact sentence with no wasted words or repetition. However, it is a fragment rather than a front-loaded verb phrase, which slightly reduces structural clarity.

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 format details are less critical, but the input side is materially incomplete. With four parameters, 0% schema coverage, and no description of project/sequence scoping, kind defaulting, or track identifier forms, an agent lacks enough context to call the tool confidently.

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% across four optional parameters, so the description must compensate. It only hints at `track` and `kind`, and omits `project` and `sequence` entirely; it also does not explain that `track` may be an integer or string or that `kind` defaults to video.

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 the resource being listed, shots/track items, and clarifies the two scopes: one specified track or every track of a given kind. It is clear enough to distinguish from a single-item getter, though it leans on the tool name for the verb and does not explicitly contrast with `get_track_item` or `delete_track_items`.

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 phrase "on one track, or on every track of `kind`" implies when to use the tool based on scope, but it does not explicitly state when to choose it over siblings such as `get_track_item` or `list_sequences`. No prerequisites or exclusions are provided.

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