clip_marker_delete

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

No annotations are provided, so the description must fully disclose behavior. It states the deletion operation but does not mention permanence, required permissions, or what happens if both frame and color are provided (e.g., does it delete only a marker matching both? The description implies two separate modes but doesn't clarify the interaction).

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 sentence that efficiently conveys the tool's capabilities. It could be slightly improved by adding a brief note about the handle parameter without becoming verbose.

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 absence of annotations and output schema, the description is incomplete. It fails to explain the mandatory handle parameter, the interaction between frame and color, and the exact behavior when color is set to 'All' (e.g., does it ignore frame?). The tool has moderate complexity, so more detail is warranted.

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 adds meaning beyond the schema by explaining that 'color' can be a colour or 'All', and 'frame' selects a specific frame. However, it does not explain the 'handle' parameter (which is required), and the relationship between frame and color when both are supplied is ambiguous.

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?

Description clearly states the action (delete), the resource (clip marker), and the two modes (by frame or by colour/all). It distinguishes this tool from sibling tools like marker_delete (which likely operates on timeline markers) and clip_marker_add.

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 on when to use this tool versus alternatives such as marker_delete or clip_marker_add. The description does not mention prerequisites or the difference between clip markers and timeline markers.

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