scroll_to_top

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core effect ('scroll to the top of the page'), which is minimally sufficient, but it does not reveal details such as whether the scroll is instant or animated, whether it operates on the main page only, or what happens on a non-scrollable page.

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. Every word earns its place, and the length is appropriate for a zero-parameter, single-action 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?

Given the tool's trivial complexity, zero parameters, and presence of an output schema, the description is nearly complete. The only notable gap is the lack of contextual guidance about how this tool relates to the many sibling scrolling and page-navigation tools, but for a no-argument action, the description covers the essential operation.

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 tool has zero parameters and the schema coverage is 100%, so there is no parameter meaning that the description needs to add. The baseline of 4 applies because the absence of parameters makes semantic explanation unnecessary.

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 states a specific verb ('scroll') and target ('top of the page'), making the tool's basic purpose clear. It does not explicitly differentiate itself from sibling scroll tools such as scroll_to_bottom or scroll_into_view, but the resource is specific enough for basic identification.

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 provides no guidance on when to use this tool versus alternatives like scroll_to_bottom, scroll_up, scroll_down, or scroll_into_view. There is no mention of exclusions, prerequisites, or typical scenarios, leaving usage entirely to inference.

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