get_timeline_gaps

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It conveys only that this is a read operation ('get'), but does not disclose what counts as a gap, whether the active sequence must be open, whether the operation is expensive, or what the returned data looks like.

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 only eight words long and is easily skimmable, but the 'Premiere Pro expanded operation:' prefix is filler that adds no information, and the remainder merely parrots the name. It is concise to the point of under-specification rather than efficiently informative.

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 and no annotations, the description alone must explain return semantics and invocation context. It never defines what 'timeline gaps' means (timecode gaps, clip gaps, missing media?), so an agent cannot confidently predict the result or decide when this tool applies.

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 0 parameters (schema is an empty object with additionalProperties true), so the baseline is 4 and there is nothing for the description to document. No misleading parameter information is present.

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 operative content, 'get timeline gaps,' is a near-exact restatement of the tool name. The 'Premiere Pro expanded operation:' prefix is boilerplate that does not explain what a timeline gap is or how this tool differs from similar siblings like get_timeline_summary and get_sequence_structure.

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 about when to call this tool, what state it requires (e.g., an open sequence), or when a sibling would be more appropriate. Among roughly 200 siblings, several get_* timeline/sequence tools exist, and the description gives the agent nothing to route on.

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