set_scroll_behavior

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

With no annotations, the description carries the full burden and does disclose key side effects the schema omits: FIXED reorders the node to last child (with flow implications in auto-layout) and SCROLLS moves a fixed node back. It stops short of covering permissions, reversibility, or what a failed call returns beyond the STICKY_SCROLLS error.

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?

Front-loaded with the core purpose, then dense side-effect detail in following sentences. Every sentence carries information, though the FIXED/SCROLLS mechanics make it somewhat dense relative to a 3-parameter tool.

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?

Complete enough for a mutation tool with no annotations and no output schema: it covers both parameter roles, the main enum behaviors, and the unsupported-value error. It leaves minor edge cases (e.g. node outside a frame, prototype-mode requirements) unstated.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining the side effects of the FIXED, SCROLLS, and STICKY_SCROLLS enum values that the terse schema descriptions do not convey.

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?

States a specific verb (Set) and resource (prototype scrolling) and separates the two distinct operations: overflowDirection on a frame and scrollBehavior on a child. An agent can immediately tell what the tool manipulates and how the two parameters differ.

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?

Gives clear conditions for using each parameter (overflowDirection on a frame, scrollBehavior on a child) and flags that STICKY_SCROLLS is unsupported and errors. It does not name any sibling tool as an alternative or state when not to use this tool, but the context of use is unambiguous.

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