figma_set_scroll_behavior

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states that scrolling is configured, without detailing side effects, dependencies (e.g., frame must be in a prototype), or whether changes are reversible. This is a minimal disclosure for a mutating 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 a single, front-loaded sentence with no filler or redundancy. It efficiently states the tool's purpose in eight words, earning a top score for conciseness.

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 tool has four parameters, including a nested scrollOffset object, no output schema, and no annotations, the description is too brief. It omits details about scrollDirection, scrollOffset, required parameters, or expected behavior, leaving significant gaps for an agent trying to invoke it 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 schema description coverage is 0%, and the description does not explain any of the four parameters. While the phrase 'scrolling for a frame' hints that nodeId refers to a frame and scrollBehavior is central, it adds little semantic value beyond the schema's enums and property names.

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 uses a specific verb ('Configure') and a clear resource ('scrolling for a frame in prototypes'), which clearly conveys what the tool does. It also distinguishes itself from sibling tools like figma_set_default_transition or figma_setup_overlay by focusing specifically on scroll behavior.

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 implies the tool is used when scrolling needs to be configured for a prototype frame, but it does not explicitly state when to use it over alternatives or mention any prerequisites or exclusions. Usage context is clear but not fully elaborated.

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