get_selected_timeline_clips

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

With no annotations, the description carries the full behavioral burden. It usefully discloses two behavioral facts an agent needs: the result depends on live selection state and on an active sequence, and it spans both video and audio tracks. It does not say what is returned when nothing is selected, whether an error is raised, or that the operation is non-mutating.

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?

One sentence, zero waste, with the scope constraint front-loaded before the track-type qualifier. Nothing to trim and nothing essential buried.

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-parameter read tool with no output schema, the definition is nearly sufficient: it tells the agent what set is returned and from where. The only real gap is the empty-selection outcome, which matters because the tool's whole premise is a conditional UI state.

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 baseline is 4. The description does add meaningful scope semantics for the implicit selection input ('currently selected', 'active sequence', 'across video and audio tracks') rather than being silent about context.

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 names a specific verb ('Get') and resource ('timeline clips (TrackItems)') and scopes it precisely to 'currently selected in the active sequence across video and audio tracks.' That scope implicitly separates it from the project-item sibling, but no sibling is named explicitly, so it stops short of a 5.

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 by the phrase 'currently selected' – an agent can infer this is the tool for reading the current timeline selection, but there is no explicit when-to-use guidance, no exclusion, and no pointer to the alternative (get_selected_project_items) for selection outside the timeline.

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