select_disabled_clips

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

No annotations are provided, so the description bears the full burden, but it only restates the operation. It does not disclose whether the selection replaces the current selection, whether it operates on the active sequence, or what happens when no disabled clips exist.

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 one short sentence and is easily scannable. The 'Premiere Pro expanded operation:' prefix is filler, but the core instruction is front-loaded and compact.

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 zero parameters and no output schema, a simple description is partially sufficient. However, the lack of detail about selection behavior and the meaning of 'disabled' leaves meaningful ambiguity for a tool that changes selection state.

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 baseline for a zero-parameter tool is 4. The description does not need to explain parameter semantics because there are none.

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 specific verb and object: 'select disabled clips.' This is clear enough, though it does not explicitly differentiate itself from the many sibling select_* tools, so it stops short of a 5.

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?

Usage is only implied: an agent would infer it should use this tool when it wants to select disabled clips. There is no explicit guidance about when to prefer this over sibling tools like select_all_clips or select_clips_by_name.

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