set_clip_selection

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

No annotations are provided, so the description carries full burden. It gives zero behavioral detail: no mention of side effects, prerequisites (e.g., active sequence), what 'expanded operation' means, or what happens to existing selection. The term 'expanded operation' is opaque and unexplained.

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 (one sentence) but it's under-specified rather than concise. 'Expanded operation' is filler that adds no meaning. It fails to earn its place because it doesn't communicate anything useful beyond the tool name.

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 tool has no parameters, no output schema, and no annotations, the description is the only source of information. It is completely inadequate for an agent to understand what this tool does, when to use it, or what the result will be. The context signals show 0 params and no schema details, so the description must carry the full load and it fails.

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 parameters, so the schema provides no parameter information. The description doesn't need to explain parameters, but it also doesn't clarify what the tool operates on (e.g., current selection, active sequence). Baseline 4 for 0 params is appropriate, though the description could have explained the implicit context.

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: set clip selection' is vague. It names the tool and says it's an 'expanded operation' but doesn't specify what setting clip selection entails (e.g., selecting clips in the timeline, setting a selection range, or defining a selection set). It doesn't distinguish from sibling tools like select_clips_by_name, select_all_clips, or set_clip_position.

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?

No guidance on when to use this tool versus alternatives. There are many selection-related sibling tools (select_clips_by_name, select_all_clips, select_clips_in_range, etc.) but the description provides no context for when 'set clip selection' is appropriate or how it differs.

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