get_timeline

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

With no annotations provided, the description carries the full behavioral burden, and it discloses very little. It does not state that this is a read-only operation, whether it needs a specific project handle or permission, how large the response can be, or whether omitted things (closed notes, unused assets) are excluded.

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?

It is short and every listed element (clips, overlays, music, notes, assets) conveys part of the payload, so nothing is padding. But it is written as a fragment rather than a front-loaded sentence, which costs clarity without saving many tokens.

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?

With no output schema, no annotations, and an undocumented required parameter, the description should do more of the work. Ambiguous terms like 'open notes' and 'assets' are left unexplained, and the agent cannot tell the expected response size or structure before calling.

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% for the single required 'project' parameter, so the description must compensate and it does not mention the parameter at all. It never says whether 'project' is a name, ID, or path, nor what happens if the project is unknown.

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 identifies the resource being returned — the complete edit with clips (timeline and source times), overlays, music, open notes, and assets — which broadly signals a full-timeline read. However, it is a noun-phrase fragment with no verb, and nothing distinguishes it from siblings like timeline_contact_sheet or check_frames beyond an implicit sense that this one is 'full'.

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?

There is no when-to-use guidance at all: no statement of what task this read serves, no exclusions, and no pointer to alternatives such as timeline_contact_sheet for a lightweight overview. An agent must infer that this is the heavy, complete read from the words 'the full edit'.

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