select_clip

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 fails to specify whether this replaces existing selections or adds to them, what occurs when no clip is under the cursor, or whether the operation is idempotent. The basic action is stated but edge cases and side effects are omitted.

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 consists of a single, efficient sentence with zero waste. It is front-loaded with the action verb and immediately specifies the target resource and spatial constraint ('under the cursor').

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 zero-parameter tool without output schema, the description adequately conveys the core operation. However, given the rich ecosystem of sibling selection tools and the ambiguity around selection behavior (replace vs. add), the description leaves meaningful gaps regarding operational context and error handling.

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 schema description coverage is 100% (trivially). Per the evaluation rules, 0 parameters establishes a baseline score of 4. No additional semantic clarification is needed or provided.

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 action ('Select') and target ('the clip under the cursor'), specifying scope at the clip level. However, it does not explicitly differentiate from sibling selection tools like select_all, select_region, or select_tracks, leaving the agent to infer the appropriate use case.

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 is provided on when to use this tool versus the five other selection-related siblings (select_all, select_region, select_tracks, etc.). There is no mention of prerequisites, such as requiring the cursor to be positioned over a clip, or what happens if no clip exists at the cursor location.

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