set_sequence_frame_rate

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

The description gives no indication of side effects, reversibility, or permissions required. Since no annotations are present, the tool's behavioral impact (e.g., modifying the sequence's metadata) is not disclosed.

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 extremely concise, consisting of a single sentence with no superfluous words. However, it is too sparse to be considered well-structured for a tool definition, omitting essential operational details.

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?

The description lacks context about the sequence scope, valid frame rate formats, or any related constraints. Given the tool's complexity and the existence of many sibling tools, this definition is severely incomplete.

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 is empty (no properties defined), and the description does not enumerate parameters. Although the tool name implies a frame rate value, its type, range, and requiredness are completely undocumented.

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 tool's function: setting the frame rate of a sequence. However, it is vague about which sequence is targeted (e.g., active sequence) and lacks detail on the acceptable frame rate values.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives, nor does it clarify any prerequisites or contextual conditions (e.g., sequence must be open).

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