set_target_track

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

Annotations are minimal (no destructiveHint, idempotentHint). Description adds behavior beyond annotations: only one per type can be targeted, implying auto-untargeting of previous. However, it does not disclose potential side effects like whether targeting affects playhead or selection.

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?

Two short, clear sentences that front-load purpose and constraint. No unnecessary words.

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 simplicity (3 params, boolean operation), description is adequate. It covers purpose, constraint, and behavior. Could mention 0-based indexing or enum values, but schema already covers them. No output schema needed.

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?

Schema coverage is 100% with descriptions for all three parameters. The description does not add extra meaning beyond the schema, so baseline of 3 applies.

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?

Description uses specific verb 'Set' and resource 'track as targeted', explains what targeted means (active for insert/overwrite edits), and adds constraint 'only one video and one audio track can be targeted at a time'. Clearly distinguishes from sibling tools like get_target_tracks and set_all_tracks_targeted.

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?

Description implies usage context (for setting targeting) and mentions constraint, but does not explicitly state when to use this tool versus alternatives like set_all_tracks_targeted or get_target_tracks, nor does it provide when-not-to-use guidance.

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