tracking.load_clip

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

Annotations provide no safety signals beyond all-false flags, and the description adds no behavioral context about side effects, scene mutation, prerequisites, or what happens after loading. 'Risk: standard; maturity: L3' is boilerplate and does not disclose the tool's actual behavior.

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 text is short, but this is under-specification rather than conciseness. Every sentence is generic harness boilerplate that could be applied to any command, and no functional information is front-loaded because there is none.

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?

Even with an output schema present, an agent cannot determine what this tool does, what the required name and path parameters represent, or where it fits in the tracking workflow. Seven parameters with no semantic explanation and a boilerplate description leave the definition fundamentally incomplete.

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 only 43%, and the core parameters name and path are bare strings with no descriptions. The description offers zero explanation of what these values mean, expected file formats, or how focalLengthPixels and _expectedSceneRevision relate to the load operation.

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 only identifies the tool as 'PartMe Blender Harness command tracking.load_clip' and lists risk/maturity metadata; it never states what the tool does. The function must be inferred from the command name alone, making the description effectively a restatement of the title.

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?

There is no guidance on when to call this tool versus tracking siblings like blender_tracking_setup_scene, blender_tracking_add_track, or blender_tracking_inspect. The only usage-related sentence is generic 'per-request argument checks and session policy still apply' boilerplate that applies to any harness command.

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