resolve_add_marker

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

The description adds that the marker is placed at an exact frame and custom data is private and optional. Annotations are minimal (all false), so description adds some value but does not cover behavior on duplicate frames, error conditions, or idempotency implications.

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 short (12 words) and front-loaded with the core action, but for a 9-parameter tool it is overly terse and could include more context without being 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 high parameter count (9) with no schema descriptions, and no guidance on output or error cases, the description is insufficient. Sibling tools are listed but not compared. The presence of an output schema is not leveraged.

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 description coverage is 0%, so the description must fully compensate. It only hints at 'custom_data' (private/optional) but ignores 8 other parameters including required 'frame'. This is inadequate.

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 action (add a timeline marker) and key constraint (at exact frame) with optional custom data. It is distinct from sibling tools like resolve_add_track or resolve_append_clips.

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, nor any prerequisites or exclusions. The description does not help the agent decide context.

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