figma_set_scroll_behavior

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

With no annotations, the description clarifies key behavioral traits: it defines each enum value (e.g., FIXED = sticky header) and specifies node type compatibility. It does not discuss side effects or error conditions, but the core behavior is well communicated.

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 concise (two sentences) and front-loaded with the main action. Every sentence adds value without redundancy or filler.

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 covers the essential usage details (parameter meanings, node types, conditional requirement). However, it omits information about the return value or success/failure indicators, which would be helpful given no output schema.

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?

Schema coverage is low (33%), but the description adds significant meaning by explaining the enum values for overflowDirection and scrollBehavior, including practical examples like 'FIXED = sticky header'. This compensates for the schema gaps.

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 sets a node's scroll behavior with explicit parameters (overflowDirection, scrollBehavior) and enums. It distinguishes itself from sibling tools by focusing specifically on prototype 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 explains the parameter meanings and node requirements (FrameNode vs SceneNode) and notes that at least one must be provided. However, it does not explicitly state when to use this tool over alternatives or provide exclusions.

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