tracking.clip_load

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the action ('load') without describing side effects, required permissions, state changes (e.g., does it add to the scene?), or what happens on success/failure.

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 8-word sentence, highly concise and front-loaded. While it could include more detail without becoming verbose, it avoids waste and communicates the core purpose efficiently.

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 2 parameters (with only schema titles), no output schema, and no annotations, the description is insufficient. It omits what happens after loading (e.g., where the clip appears), error conditions, and how the 'name' parameter interacts with the loaded clip. For a load operation, more context is 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 description coverage is 0%, so the description should compensate. It partially does by clarifying the path expects a movie clip or image sequence source, but it adds nothing about the name parameter (only mentioned in schema title). The description does not elaborate on accepted formats, path resolution, or constraints.

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 uses a specific verb ('Load') and resource ('movie clip or image sequence source'), clearly identifying the tool's function. However, it does not explicitly distinguish from sibling tools like tracking.clips, which likely lists clips. It's clear but could be more precise about what 'load' entails.

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 provided on when to use this tool versus alternatives (e.g., tracking.clips for listing, or other load mechanisms). There is no mention of prerequisites, typical use cases, or when not to use it.

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