Set Sequence Frame Rate

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only the 'active sequence' target, saying nothing about whether existing clips are conformed, retimed, or left untouched — a meaningful behavioral unknown for this mutation.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity contributes to the missing usage and behavioral context rather than being optimized for it.

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?

With an output schema present and annotations covering the safety profile, the definition is minimally sufficient to call the tool. It does not resolve the sibling overlap (set_override_frame_rate, set_sequence_settings) or note any effect on existing sequence content, which leaves real gaps.

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% and the single parameter includes an example list of common frame rates plus min/max bounds, so the schema does the heavy lifting. The description adds no syntax or format guidance beyond it, which is the baseline-3 case.

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?

States a specific verb (Change) and resource (frame rate of the active sequence), which is clear enough to act on. It does not distinguish itself from close siblings like set_sequence_resolution or set_override_frame_rate, so an agent must infer which one applies from the name alone.

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 description gives no when/when-not guidance and never mentions nearby alternatives such as set_override_frame_rate or set_sequence_settings, which affect frame-rate-adjacent settings. The agent is left to guess which frame-rate tool is correct.

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