tracking-clip_load

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Load' but does not mention side effects (e.g., replacing an existing clip), required permissions, error behavior for missing files, or whether the clip is added to the current scene. This is insufficient for an agent to anticipate outcomes.

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, succinct sentence with no redundancy. It is front-loaded and to the point. It could arguably be too terse, but for such a simple tool it is appropriately concise, earning a high score without being verbose.

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 tool is simple, but given no output schema and no annotations, the description should provide more context: where the clip is loaded (current scene? tracking data?), accepted formats, and any consequences. It only states the action and resource, leaving significant gaps for an agent to understand the full impact.

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%, so the description must compensate for parameter clarity. It does not explain the 'name' parameter's purpose or provide context for 'path' beyond implying a file path. The schema only gives titles, which are minimal. The description fails to add meaningful parameter semantics beyond what the schema already shows.

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 ('Load') and the resource ('a movie clip or image sequence source'). It is specific and distinguishes from sibling tools like tracking-clips (which lists clips) and tracking-report (which provides status). The verb-noun pair is unambiguous.

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 given on when to use this tool versus alternatives, such as prerequisites (e.g., must have a tracking setup) or whether this is the first step in a tracking workflow. Sibling tools like tracking-marker_report and tracking-track_report imply different uses, but the description does not clarify.

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