Create LTC timecode bridge

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

The description adds meaningful behavioral context beyond the annotations by specifying that the tool creates a scaffold with placeholders and routing notes, implying it does not produce a fully functional LTC bridge. This is useful for setting agent expectations. Annotations only indicate readOnly=false and destructive=false, which the description does not contradict.

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 sentence that front-loads the action ('Create') and the object ('LTC receive/generate scaffold'), with the supporting components listed in a compact phrase. No wasted 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?

With 8 parameters, no output schema, and minimal annotations, the description is incomplete. It explains what the scaffold contains but does not mention prerequisites, return values, or the meaning of key parameters like active or frame_rate, leaving an agent with significant ambiguity for a relatively complex creation 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 schema has low description coverage (25% of 8 parameters), so the description must compensate. It partially does by mentioning 'receive/generate' (mode) and 'LTC In/Out' (devices), but it does not explain the semantics of active, cue_count, frame_rate, input_device, output_device, or parent_path beyond what the sparse schema provides.

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 creates an LTC receive/generate scaffold with specific components (LTC In/Out CHOP placeholders, cue maps, routing notes). The verb 'create' and resource 'LTC receive/generate scaffold' are specific and distinguish it from sibling creation tools like 'create_cue_sequencer' or 'sync_timecode'.

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 implies its usage by stating what it creates (an LTC receive/generate scaffold), so an agent can infer it is for setting up LTC timecode bridges. However, there is no explicit when-to-use guidance or differentiation from alternatives like 'sync_timecode' or 'add_timecode_overlay'.

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