set_sequence_frame_rate

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

The description states 'Change', which implies a mutation, consistent with readOnlyHint=false. However, it does not disclose behavioral details such as whether the frame rate change triggers re-interpretation of clips, requires a specific sequence state, or has other side effects. The annotations provide basic safety info, but the description adds no additional behavioral 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, straightforward sentence with no unnecessary words. It effectively communicates the core function without redundancy.

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 tool with one well-documented parameter and clear annotations, the description is nearly complete. It states the action and the target (frame rate of active sequence). While it could mention that the sequence must be active or that changes affect the timeline, the current level is sufficient for basic understanding.

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 input schema has 100% coverage with a detailed description and examples for the only parameter. The description adds no new meaning beyond what the schema provides, so it meets the baseline expectation without adding extra value.

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 'Change the frame rate of the active sequence' uses a specific verb ('Change') and clearly identifies the resource (frame rate) and context (active sequence). It distinguishes itself from sibling tools like set_sequence_settings, which handles multiple sequence properties, by focusing solely on frame rate.

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 is provided on when to use this tool versus alternatives like set_sequence_settings, nor does it mention prerequisites (e.g., an active sequence must exist). The description implies usage by stating the action, but fails to set explicit context or exclusions.

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