scroll_to_bottom

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action itself, omitting details such as whether the scroll is instantaneous or animated, whether it triggers any events or lazy loading, or whether it operates on the main page only. This is minimal behavioral transparency.

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, short sentence with no wasted words. It is front-loaded and immediately conveys the complete action. It could not be briefer while retaining meaning.

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 zero-parameter tool, the description is minimally adequate: it names the action and target. However, given the wide range of sibling scrolling tools, some context about when to choose scroll_to_bottom over alternatives would improve completeness. The missing usage guidance detracts from full contextual richness.

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, so there are no parameter semantics to clarify. The description correctly adds no redundant parameter information, and the schema fully covers the empty property set. A baseline score of 4 is appropriate for a no-parameter tool.

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 action: scroll to the bottom of the page. It specifies a concrete resource (the page bottom) and is easily distinguished from sibling tools like scroll_to_top, scroll_up, and scroll_down. The purpose is unambiguous and directly matches the tool name.

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 usage guidance is provided. The description does not state when to use this tool versus scroll_down, scroll_into_view, or scroll_to_top, nor does it mention any caveats like lazy-loaded content or scrollable containers. The agent receives no explicit decision-making support.

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