stabilize

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

No annotations provided, so the description carries full burden. It fails to disclose behavioral traits such as whether the stabilization modifies the clip in place, is reversible, or has side effects. The requirement for DaVinci Resolve Studio is mentioned but is not sufficient to understand the tool's 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 description is concise with two sentences, front-loading the primary purpose. The second sentence lists the parameters, which is acceptable but could be more structured. Overall, it is appropriately sized.

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 has 3 parameters and no annotations, and the description does not mention return values or output behavior. Although an output schema exists (not shown), the description lacks completeness for a stabilization operation, such as whether it succeeds silently or returns a status.

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%, but the description groups the three parameters as 'Clip locator', providing context that they identify a timeline item. However, it does not explain each parameter individually (e.g., what track_type values are valid). This adds some meaning beyond the bare schema.

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 verb 'apply stabilization' and the resource 'timeline item', specifying the technology 'DaVinci Neural Engine' and the requirement for DaVinci Resolve Studio. It distinguishes from siblings like 'smart_reframe' which is a different operation.

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 mentions a prerequisite (DaVinci Resolve Studio) but does not provide guidance on when to use this tool versus alternatives, nor does it specify scenarios where stabilization is appropriate or not.

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