set_sequence_framerate

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action without detailing side effects, persistence, scope (e.g., whether it modifies the asset or just the viewport display), or any constraints. The word 'display' introduces ambiguity about whether this alters the underlying sequence asset.

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, concise sentence with no redundant information. It states the essential purpose without fluff.

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 tool is a simple setter with full schema coverage, but the description lacks crucial context such as when the change takes effect, whether a save is required, what errors could occur, or how 'display frame rate' differs from related sequence properties. For a mutation tool with no annotations or output schema, this is insufficient.

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 provides complete descriptions for both parameters (fps as 'Frames per second' and sequence_path as 'LevelSequence asset path'), so the schema already covers the semantics. The description adds no additional meaning or relationships beyond that baseline.

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 verb 'Set' and the specific resource 'display frame rate of a sequence,' making the tool's purpose unambiguous. It also differentiates from sibling tools like set_playback_range, which target a different sequence property.

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 provides no context on when to use this tool vs alternatives, no prerequisites, and no mention of circumstances that would favor this over other sequence-oriented setter tools. It offers no exclusionary or alternative guidance.

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