session_scroll

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

No annotations are provided, so the description carries the full transparency burden. It usefully discloses that the tool waits for lazy content to load ('Ждёт догрузку lazy-контента') and requires session_start. However, it does not explain whether scrolling is incremental or absolute, how max_chars affects behavior, or what happens if the session is no longer active.

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 three short sentences and every sentence earns its place: what the tool does, one behavioral nuance (lazy-content waiting), and a prerequisite. It is front-loaded and has no redundant filler.

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 the return shape may be covered elsewhere. The description adequately captures purpose, prerequisite, and lazy-loading behavior, but the unexplained max_chars parameter and lack of annotations leave a meaningful gap in what an agent needs to invoke the tool confidently.

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%, so the prose description must supply parameter meaning. It adds some value by listing 'bottom/top/down/up', which clarifies the direction parameter. However, max_chars is completely unexplained, and the description does not formally map any of its prose to the schema properties, leaving the agent guessing about a key parameter.

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 on the live session page) and enumerates the direction values bottom/top/down/up. It distinguishes session_scroll from nearby session_navigate/session_text tools by focusing specifically on scrolling, though it does not explicitly contrast itself with alternative tools.

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 gives a clear prerequisite: 'Требует session_start' (requires session_start), and scopes the tool to the live session page. It does not state when not to use it or name alternatives, but the context is sufficient for an agent to understand that this tool operates only on an already-started live session.

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