delete_marker

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It correctly indicates a destructive action, but it omits important behavioral details such as irreversibility, behavior when no marker exists at the frame, and behavior when multiple markers share the same frame.

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?

A single efficient sentence with no filler. The verb and object are front-loaded, and every phrase adds relevant operational detail.

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 simple one-parameter tool and existing output schema, the description is mostly adequate. Gaps around missing markers, multiple markers at the same frame, or destructive consequence are left unaddressed, so a cautious agent still lacks some operational edge-case 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 defines frame only as an integer with 0% coverage, so the description must add meaning. It adds the crucial semantic that frame is measured relative to timeline start, which meaningfully helps an agent provide a correct value.

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 the timeline marker') and a precise location ('at a frame relative to timeline start'), making the resource and target unambiguous. It also naturally distinguishes itself from the sibling add_marker tool.

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 intended use is implied by the delete verb and marker resource, so an agent can infer when it applies. However, it never explicitly states when to use it over alternatives, edge conditions, or prerequisites.

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