set_overflow_direction

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

With no annotations provided, the description carries the full behavioral burden, but only discloses that this affects prototype scrolling. It omits permission requirements, whether changes are reversible/undoable, and any interaction with existing scroll settings.

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?

A single front-loaded sentence with the enumeration parenthetically appended; efficient and free of filler, though the parenthetical is slightly awkward phrasing.

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?

For a simple two-parameter setter with no annotations and no output schema, the enum values are the key addition, but the absence of any frameId or behavioral context leaves the definition only marginally complete.

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 0%, so the description must compensate. It helpfully enumerates the accepted values for overflowDirection (NONE, HORIZONTAL, VERTICAL, BOTH), which the schema lacks, but says nothing about frameId (format, source, required-ness beyond the schema).

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 (frame overflow direction) and clarifies it governs scrolling in a prototype, enumerating the four valid modes. An agent can grasp the operation, though it doesn't explicitly differentiate itself from adjacent prototype/scroll siblings.

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 on when to use this versus alternatives, no prerequisites (e.g. the frame must be a prototype frame), and no mention of what happens if the frame already has a direction set. Usage is only implied by 'prototype'.

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