select_clip

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

The description does not disclose side effects, such as whether the previous selection is replaced or extended, or whether it affects multiple clips. With no annotations, the agent lacks information about the tool's read/write nature and impact on the project state.

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 a single, concise sentence with no unnecessary words. It directly states the action and target without ambiguity, making it easy to read and process.

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?

The description is minimal and lacks context about the selection behavior (e.g., does it deselect others? Does it work on the active track?). While the tool name provides some hints, the description alone does not fully equip an agent to understand the implications of invoking the tool.

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 input schema has no parameters, so the description does not need to explain any. It adds no extra meaning beyond the empty schema, but since there are no parameters, this is adequate. The score reflects a neutral baseline without missing parameter information.

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 clearly states the action (select) and the target (clip under cursor), distinguishing it from other selection tools like select_all or select_none. However, it could be more specific about what constitutes a 'clip' in the context of the application, though it is likely understood.

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 alternative selection methods (e.g., select_all, select_region). The description does not mention any preconditions or contexts where this tool is preferred.

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