instagram_scroll

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

Annotations already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral signal, that the result is fresh element references valid after the scroll, but says nothing about how far it scrolls, whether it waits for loading, or what happens at page end.

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?

One short sentence with the action front-loaded and no filler. It is efficient, though the brevity comes partly at the cost of missing detail rather than from tight editing.

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?

An output schema exists, so return values need not be described, but for a browser-automation tool with two undocumented required parameters the description leaves critical invocation details unaddressed. The 'fresh references' note is the only clue about post-scroll state.

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 description coverage is 0% for two required parameters. 'direction' is loosely implied by the word 'scroll,' but 'expected_account' is entirely unexplained in both schema and description, leaving the agent to guess that it is an account-verification guard.

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 names a specific action (scroll) and target (the current Instagram page), which cleanly separates it from siblings like instagram_press, instagram_click, and instagram_screenshot. The trailing phrase 'obtain fresh references' hints at the outcome but stays vague about what a reference actually is.

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?

There is no indication of when to scroll versus using a sibling such as instagram_snapshot or instagram_read_post, nor any stated preconditions. The only guidance is implicit in the verb 'scroll,' which an agent must interpret on its own.

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