set_sequence_frame_rate

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

With no annotations, the description must disclose behavioral traits, but it only repeats the action. It doesn't state whether the frame rate is applied to the active sequence, whether any confirmation occurs, or what side effects may result. This is a complete absence of behavioral information.

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 short but not effectively so. It is merely a restatement of the tool name and does not earn its place by adding value. Under-specification is not conciseness; the sentence is wasteful because it provides no novel information.

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?

Given the large context of sibling tools and lack of annotations/output schema, the description is severely incomplete. It fails to mention which sequence is affected, how the target frame rate is communicated, or any prerequisites. There is no meaningful guidance for an agent to use this tool correctly.

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 tool has 0 parameters, and the schema description coverage is 100%. With no parameters to document, the baseline is 4. The description could have explained how the frame rate is determined (e.g., from current project settings), but the absence of parameters reduces the burden.

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 restates the tool name as 'set sequence frame rate' without adding any new information. It specifies the verb and resource but does not distinguish from sibling tools like set_sequence_settings or set_sequence_resolution. The phrase 'Premiere Pro expanded operation' is generic and does not clarify the tool's unique role.

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?

There is no guidance on when to use this tool versus alternatives. For example, set_sequence_settings could set the frame rate along with other properties, but no exclusions or preferences are mentioned. The description provides no context for tool selection.

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