tracking.load_clip

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

The description mentions 'Risk: standard; maturity: L3' and 'requirements' but these are generic operational notes, not behavioral disclosures. It does not describe side effects, permission needs, or what happens to the scene. The annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no further behavioral context, such as whether the clip is loaded into the current scene or a new one.

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 extremely short, but this is under-specification rather than conciseness. While it front-loads the command name, it provides no substantive content. Every sentence is generic boilerplate that applies to all commands in the harness, so it earns no value for brevity.

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 the tool's purpose (loading a tracking clip) and the presence of a nested object for `path` and other parameters, the description is severely incomplete. It does not explain what the tool does, what the output schema returns, or any side effects. The agent cannot make an informed call without additional research.

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 description says nothing about any of the seven parameters. With schema description coverage at only 43%, the description should compensate by explaining what `name`, `path`, `focalLengthPixels`, etc. mean, but it does not. The agent is left to infer parameter semantics entirely from the schema, which lacks descriptions for most parameters.

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 merely restates the command name `tracking.load_clip` without any indication of the tool's function. It does not state what action is performed, what resource is affected, or what 'loading a clip' entails. There is no verb beyond the name itself, making it a tautology.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusion criteria. An agent has no basis to decide between this and other tracking tools like blender_tracking_add_track or blender_tracking_setup_scene.

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