timeline_get_current

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral details: it returns None when no timeline is open, and it specifies the exact dictionary keys (name, start_frame, end_frame, video_tracks, audio_tracks, start_timecode). This goes beyond what annotations provide and sets clear expectations for the return value.

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 for purpose and one for return structure. It is front-loaded with the most important information and contains no filler or redundant text.

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 simple read-only tool with no parameters and a provided output schema, the description is fully complete. It explains the primary behavior, the edge case (None), and the return structure, leaving no significant gaps.

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 has no parameters, and the empty schema covers all cases (100% coverage). The 0-parameter baseline is 4, and the description correctly avoids adding unnecessary parameter details since there are none to describe.

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 tool returns info about the current timeline, with a specific verb ('Return info') and resource ('current timeline'). It also distinguishes from sibling tools like timeline_get_by_index or timeline_get_name by focusing on 'current' and listing the full set of returned keys.

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 description implies when to use this tool (when you need the current timeline's info) by using the word 'current,' which differentiates it from timeline_get_by_index and timeline_get_count. However, it does not explicitly mention alternatives or provide exclusion criteria, so it falls short of a 5.

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