set_fps

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

With no annotations, the description must disclose behavioral traits. It only says 'Set the scene frame rate' without explaining side effects, required scene state, whether it affects playback or rendering, or if it is destructive. The agent has no information about potential impacts on existing animations, keyframes, or render settings, which is a significant gap for a mutation tool.

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: a single sentence for the purpose and a single-line parameter description. It is front-loaded and contains no filler. While it could be structured more richly, it is appropriately sized for a one-parameter tool and avoids unnecessary detail.

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 is sufficient to call the tool with the correct parameter, but it does not explain what the frame rate affects in the broader scene context (e.g., animation timing, render output). Given the tool's simplicity and lack of output schema, it is minimally adequate, but the lack of clarification on the setting's impact and relationship to other animation tools makes it incomplete for an agent operating in a large tool suite.

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 schema has no description for the fps parameter (coverage 0%), so the description compensates by explaining its meaning and providing a valid range (1-1000). This adds value beyond the schema's basic type and default. However, it does not elaborate on the parameter's effect (e.g., whether it sets playback speed or render output rate), so it is helpful but not exhaustive.

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 action (Set) and the specific resource (scene frame rate). It is distinct from siblings like set_animation_range or set_interpolation because it uniquely targets the frames-per-second setting. The phrasing 'Set the scene frame rate' is specific and avoids tautology, though it could be slightly more explicit about the context (animation vs render).

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 given on when to use this tool versus alternatives. There is no mention of scenarios where set_fps is preferred, nor any exclusions (e.g., 'use set_animation_range for start/end frames'). The description implies usage only by stating the purpose, but does not help the agent differentiate from many closely related animation tools in the sibling list.

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