Create YOLO ONNX tracker scaffold

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

While annotations indicate readOnlyHint=false and destructiveHint=false, the description adds significant behavioral context beyond those flags. It states the scaffold is 'deterministic', lists the exact network nodes it creates, and discloses the limitation that live detection depends on external components. This provides transparency about what the tool actually does and its operational requirements.

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 compact and efficient: a direct opening sentence, a concise list of created components, and a final sentence covering the live detection requirement. No filler or redundancy. Every sentence contributes useful information.

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 tool with 10 parameters, all fully documented in the schema, and with annotations covering read/destructive hints, the description provides a solid overview of the build output and the key operational prerequisite. It doesn't explain what 'deterministic' means in practice or detail the scaffold's default state, but the essentials are covered. It is complete enough for an agent to understand the tool's role and limitations.

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 100%, so the baseline is 3. The description mentions outputs like 'source input' and 'backend receiver placeholder' that map to parameters (input_top_path, backend), but it doesn't explain parameter values, defaults, or usage beyond what the schema already documents. All parameter semantics are adequately handled by the schema; the description adds no additional parameter-level meaning.

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 a specific verb ('Build'/'Creates') and a specific resource ('deterministic TouchDesigner scaffold for YOLO-style object tracking'). It enumerates the key created components (source input, backend receiver placeholder, detections DAT, stable tracks_out CHOP channels, annotated_out TOP, setup notes), which distinguishes it from generic create_* siblings. The purpose is unambiguous and differentiated.

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 gives clear context that this tool is for building a YOLO/ONNX tracker scaffold and includes an important when-not condition: 'Live detection requires an external detector or validated TouchDesigner Python ONNX runtime.' This implies the scaffold alone isn't sufficient for live detection, providing a practical boundary. It does not explicitly name alternative tools, but the context is sufficient for selection.

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