get_timeline_gaps

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses nothing: no side effects, return format, safety profile, or edge cases. Even for a read-only operation, the agent has no idea what a 'gap' means or what data will be returned.

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 short, but this is under-specification, not effective conciseness. It wastes its single sentence by restating the name rather than providing substance. A good description should front-load meaning; this one offers none.

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?

Given the absence of an output schema, annotations, and any meaningful description, the tool is completely under-specified. The agent cannot infer what data is returned, what conditions define timeline gaps, or how this tool relates to siblings like get_timeline_summary. This is a severe completeness gap.

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 0 formal parameters, and the schema allows arbitrary additional properties but defines none. Per the rubric, a baseline of 4 applies when there are no parameters, since the description does not need to explain parameter details. No additional parameter semantics are required.

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 'Premiere Pro expanded operation: get timeline gaps' merely restates the tool's name with an unhelpful 'expanded operation' prefix. It does not define what timeline gaps are, what the tool returns, or how it differs from numerous other 'get' tools like get_timeline_summary or 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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, expected context, or scenarios where timeline gaps are relevant. It is a complete absence of usage direction.

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