extract_selection

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

No annotations are provided, so the description carries full responsibility. It does not disclose that this is a timeline-mutating operation, whether it closes gaps, whether it is undoable, or any other side effects. The phrase 'expanded operation' is meaningless without specifics.

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 under-specified rather than concise. It provides no actionable information, so efficient phrasing is irrelevant. It fails to front-load any useful content, making it more of a placeholder than a concise definition.

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 an operation that likely mutates the timeline, this description is severely incomplete. There is no explanation of inputs, outputs, behavior, or distinctions from similar tools, leaving an agent completely unable to use it correctly.

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 schema defines zero parameters and is an open object, so the description adds no parameter semantics. Per rubric, 0 params yields a baseline of 4; the description adds no additional information, but there is nothing to document.

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: extract selection' merely restates the tool name with no indication of what the operation actually does, what it affects, or how it differs from siblings like lift_selection. It is a tautology, not a purpose statement.

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 extract_selection versus alternatives such as lift_selection or ripple_delete. No mention of typical workflows, prerequisites, or scenarios, so the agent gets no help choosing this tool.

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