browser.get_container_scroll_state

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

No annotations are provided, and the description only states the basic function. It does not disclose potential side effects, error behavior (e.g., invalid selector), or any requirements (e.g., page must have scrollable containers). The behavioral burden is not addressed.

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 concise sentence with no unnecessary words. It efficiently conveys the core purpose.

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?

Lacking an output schema, the description should explain what metrics are returned (e.g., scroll top, scroll height). It does not. Additionally, no context is provided about prerequisites or usage flow with sibling tools.

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 sole parameter 'selector' lacks any explanation in the schema or description. The description does not define what format the selector expects (e.g., CSS, XPath), leaving ambiguity. With 0% schema description coverage, the tool should compensate but fails to do so.

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 ('Get scroll metrics') and the target ('a specific scrollable container'), distinguishing it from siblings like 'get_scroll_state' (page-level) and 'get_scrollables' (list containers). However, it could be more explicit about the type of metrics returned.

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 tool versus alternatives like 'get_scroll_state' or 'scroll_container'. The description does not differentiate usage contexts or provide any prerequisites.

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