scroll_page

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

With no annotations, the description carries full burden but only mentions direction and amount without explaining behavior (e.g., whether scrolling is smooth or instant, whether it works in all contexts, or what the amount unit is). This lacks critical detail for an agent to anticipate tool effects.

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 very short and to the point, but the structure could be improved (e.g., separating the general purpose from parameter details). While no words are wasted, the brevity leads to missing information.

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 has two parameters and no annotations, the description is too minimal to be considered complete. It lacks behavioral details, parameter explanations, and clarity on the output schema (though that may help with return values). The tool is simple, but more context is needed for reliable use.

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 description partially covers the 'direction' parameter by listing its valid values inline, but it provides no explanation for the 'amount' parameter (default 500, but unit is missing). Since schema description coverage is 0%, the description fails to compensate adequately.

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 tool scrolls the page and lists the direction options (up/down/top/bottom). However, it does not distinguish from the sibling tool 'scroll_to', which might scroll to a specific element rather than by direction.

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 indicate when to use scroll_page versus alternatives like scroll_to or navigate, nor does it mention any prerequisites or exclusion criteria.

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