get_timeline_items

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states it lists items, omitting whether it's read-only, any permissions required, or side effects. The lack of annotation coverage leaves the agent inferring 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?

Two sentences and a compact bullet list for parameters. Every sentence adds value with no filler. Front-loaded: immediate action and object.

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 the presence of an output schema, the description need not detail return values. For a simple list tool, it covers the essentials (what, how to specify track). Minor gap: no mention of behavior when track doesn't exist or timeline is empty, but output schema likely covers structure.

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?

Input schema has 0% description coverage, but the description adds full meaning: track_type with allowed values and default, track_index with 1-based indexing and default. This compensates for the schema gap, though it could be more explicit about constraints (e.g., integer range).

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 'List all clips/items on a specific track of the current timeline,' identifying the specific verb (list) and resource (items on a track). It distinguishes from sibling tools like get_current_timeline_info or get_timeline_item_properties, though not explicitly, but the purpose is unambiguous.

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?

No guidance on when to use this tool vs alternatives. It does not mention prerequisites (e.g., timeline must exist) or scenarios where alternative tools like get_timeline_item_properties (for a specific item) might be preferred. The description is purely operational.

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