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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it is exceptionally thorough: it explains ripple-delete effects, keyframe/marker/audio-overlay shifting, layer trimming versus splitting, audio-overlay truncation, the speed-ramp refusal, composition-length shrinking, and frame indexing/clamping. This is far beyond what the schema conveys and leaves little hidden 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 core action is front-loaded in the first line, and every subsequent clause adds a distinct behavioral or edge-case fact rather than restating the schema. Although dense, the description is appropriately sized for the complexity of a ripple-delete operation with source-aware splitting and refusal conditions.

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 no annotations and no output schema, the description is remarkably complete for invocation: it covers coordinate conventions, clamping, inclusive/exclusive boundaries, affected element types, layer-specific behavior, refusal conditions, and length-shrinking consequences. An agent has enough information to call this tool correctly and predict its side effects.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: frames are '0-indexed project-timeline frames at 30 fps', endFrame is exclusive and clamped, and the delta calculation is defined. This clarifies how the two numeric parameters interact and what coordinate space they live in.

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 opens with a specific verb and resource: 'Ripple-delete a time window [startFrame, endFrame)' on the project timeline, clearly defining the operation and its NLE semantics. It further distinguishes itself from sibling mutation tools by detailing source-aware layer trimming/splitting and the refusal on speed-ramp keyframes, so an agent can unambiguously identify what this tool does.

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 gives clear operation context and an explicit when-not condition: it 'REFUSES to cut across a video layer that carries speed-ramp keyframes' and prescribes the remedy ('remove them, or cut outside that layer's span, first'). It does not name alternative sibling tools, so it stops short of fully explicit alternative routing, but the constraints are actionable enough for correct selection.

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