timeline_delete_marker

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

The description simply states the action without disclosing error behavior (e.g., what happens if no marker exists at the given frame), whether the deletion is permanent, or any effects on associated data. With no annotations, this minimal disclosure is insufficient.

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, clearly worded sentence that directly states the tool's action. No wasted words.

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 description is incomplete for a destructive operation; it does not address edge cases, preconditions, or effects on the timeline. The presence of an output schema does not compensate for missing behavioral context.

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 schema provides full documentation for the single parameter frame_id with its description. The tool description adds little beyond what the schema already states, so the baseline 3 is appropriate.

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 uses a specific verb ('Delete'), identifies the resource ('a marker'), and specifies the scope ('on the current timeline'). This clearly distinguishes it from sibling tools like clip_delete_marker and item_delete_marker, making the purpose unambiguous.

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 is provided about when to use this tool versus alternatives such as clip_delete_marker or item_delete_marker. There are no prerequisites mentioned (e.g., needing an active timeline) nor exclusions.

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