davinci_add_beat_marker

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

With no annotations provided, the description carries the full burden. It states the action but fails to disclose potential side effects (e.g., overwriting existing markers), prerequisites (e.g., an open timeline), or return behavior. This lack of detail leaves the agent uncertain about the tool's operational context.

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, focused sentence that gets straight to the point. It uses an active verb and communicates the core function without any extraneous words or details.

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?

For such a simple tool, the description is minimally adequate—it states what it does and where. However, it omits any mention of return values, success/failure indicators, or required timeline state, which could be important in a larger workflow. The presence of an output schema is noted but not detailed in the description, so the agent is not fully informed.

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 no per-property descriptions, so the description must clarify all parameters. It only explains 'frame' as the frame number, leaving 'note' and 'color' unexplained. While their names and defaults are suggestive, the description does not compensate for the schema's low coverage.

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 'Adds' and the specific resource 'editorial marker' with location 'on the timeline at the given frame number'. This leaves no ambiguity about the tool's purpose and distinguishes it from sibling tools that analyze or build beat-synced reels.

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?

There is no explicit guidance on when to use this tool versus alternatives such as davinci_build_beat_synced_reel or davinci_analyze_audio_beats. The description implies usage for placing a marker at a specific frame, but it does not mention any conditions or mention when not to use it.

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