get_next_edit_point

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'get next edit point,' which implies a read operation but discloses nothing about what is returned, whether the playhead moves, which sequence is queried, or how edge cases (no next edit point) are handled. This falls short of minimal behavioral transparency.

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 short, but it does not earn its place: 'Premiere Pro expanded operation' is filler, and 'get next edit point' merely repeats the tool name. It is under-specified rather than effectively concise, and it lacks any useful structure or additional detail.

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 params, no output schema, and no annotations, the description needed to clarify context (which sequence, which edit point, relative to what) and return semantics. It does neither. Compared to other timeline inspection tools, this description is incomplete and leaves an agent guessing about expected behavior and output.

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 declared parameters, so the baseline for this dimension is 4. The description does not add parameter-specific meaning, but no parameters exist to document. It could have clarified implicit context like the active sequence or playhead, but the absence of parameters means the schema imposes no parameter burden.

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 states a clear verb and resource ('get next edit point'), but it is essentially a restatement of the tool name plus the boilerplate 'Premiere Pro expanded operation.' It lacks critical context such as what 'next' is relative to (playhead? selected clip?) and how it differs from siblings like get_clip_at_playhead or move_playhead_to_edit. This is a vague purpose rather than a fully distinguishing one.

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. The description does not mention the active sequence, playhead position, timeline context, or any exclusions. With dozens of related timeline and edit-point tools among siblings, the lack of usage criteria is a clear gap.

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