get_timeline_summary

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'get,' implying a read operation, but gives no details about side effects, whether it requires an active timeline, how the summary is structured, or what operational constraints exist. The description adds almost no informational value beyond the tool name.

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 very short and front-loaded, which is good for conciseness. However, 'Premiere Pro expanded operation' is a redundant/noisy prefix, and the remaining text merely restates the tool name. It is under-specified rather than efficiently concise.

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 tool with no parameters, no annotations, and no output schema, the description should clarify what 'timeline summary' means, whether it depends on an active sequence, and how it relates to similar inspection tools. None of that is present, so an agent cannot reliably distinguish this tool from other sequence/timeline queries.

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 zero parameters and the schema is an empty object, so there is nothing for the description to clarify. Per the baseline for zero-parameter tools, the description is adequate on this dimension even though it offers no parameter explanations.

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 is essentially a restatement of the tool name: 'get timeline summary.' It does not define what a timeline summary contains or what distinguishes this from related tools like get_sequence_structure or get_full_sequence_info. The 'Premiere Pro expanded operation' prefix provides a product context but not a functional definition.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., open project, active sequence), expected output, or compare against sibling tools. The phrase 'expanded operation' is not a usage guideline.

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