set_start_time

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description's 'Set' implies a write operation but no destructiveness. The description adds nothing beyond what annotations already imply; it does not disclose side effects, undo behavior, or permission requirements, which is acceptable for a simple parameter-setting tool but not exemplary.

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, well-constructed sentence that conveys the essential action without superfluous words. It is front-loaded and efficient.

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 a simple setter tool with no output schema, the description is adequate but could be more complete by distinguishing it from similar tools (e.g., 'set_clip_start_time'). Given the large number of sibling tools, additional context about scope or effects would improve completeness.

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 coverage is 100% with clear parameter names and descriptions. The description adds 'timecode offset' context but does not enhance understanding of parameter semantics beyond the schema, earning the baseline score.

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 ('Set the start time') and the resource ('project item'), with the parenthetical 'timecode offset' adding specificity. While it differentiates from sibling 'set_clip_start_time' by targeting 'project item' versus 'clip', the distinction is subtle and could be more explicit.

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 like 'set_clip_start_time' or other tools. The description gives no context about prerequisites, typical use cases, or when not to use it, leaving the agent without decision support.

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