set_zero_point

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

Annotations already indicate the tool is not read-only and not destructive. Description adds minimal behavioral context, only clarifying that it sets the 'zero point' for timecode. No discussion of side effects, required permissions, or how existing timecode is affected.

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?

Description is a single sentence that is efficient and front-loaded. No redundant information.

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 no output schema, the description does not explain what the tool returns (if anything). It also omits constraints (e.g., valid range for start_seconds) and interaction with sequence state. For a tool with two parameters, more context is needed for full usability.

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 100% with both parameters documented. Description does not add extra semantic information beyond the schema. Baseline score of 3 is appropriate as schema handles parameter details adequately.

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 tool sets the starting timecode (zero point) of a sequence. Verb 'Set' and resource 'starting timecode (zero point) of a sequence' are specific and distinguishable from sibling tools like set_start_time and set_clip_start_time, which operate on 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 such as set_start_time or set_sequence_in_out_points. The description lacks context about prerequisites (e.g., active sequence) or exclusions.

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