lock_track

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

No annotations are provided, so the description carries full burden. It describes the basic action but omits side effects, error handling, or requirements (e.g., behavior if track index is out of range, whether locking affects editing).

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 concise: one sentence plus an argument list with no extraneous information. It is front-loaded with the action, then lists parameters. Every sentence serves a purpose.

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's low complexity and existence of an output schema (not shown), the description is minimally adequate. It covers the core action but could mention edge cases or common usage patterns to be fully complete.

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 description coverage is 0%, but the description adds meaningful context: track_type is clarified as 'video', 'audio', or 'subtitle'; index is stated as 1-based; locked's boolean semantics are explained. This significantly adds value beyond the bare schema.

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 tool locks or unlocks a track, using specific verbs 'lock/unlock' and specifying the resource 'track in the current timeline'. It effectively distinguishes from siblings like add_track or delete_track.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., enable_track). It does not specify prerequisites, such as requiring an open timeline or track existence.

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