scroll

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

The description mentions scrolling 'by pages' and 'in a direction', giving some behavioral clues. But it doesn't explain what 'pages' means, whether it's smooth or instant, or how 'element_index' affects behavior. Since no annotations exist, the description carries full burden and is insufficient.

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, which is concise, but it omits critical information like parameter details. It is front-loaded but lacks substance.

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 4 parameters and no output schema, the description is too sparse. It doesn't explain return values, prerequisites (e.g., app must be active), or how to use optional parameters like 'pages' or 'element_index'. Incomplete for confident usage.

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?

With 0% schema description coverage, the description should compensate but only mentions 'pages' and 'direction' without details. It doesn't explain 'app', 'element_index', or valid values for 'direction'. The parameter semantics are unclear.

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 verb 'scroll' and the resource 'active app', with modifiers 'by pages in a direction'. However, it does not distinguish this tool from siblings like 'drag' or 'press_key' which might also affect scrolling.

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 explicit guidance on when to use this tool versus alternatives. The description only states what it does, not when to prefer it over e.g., 'drag' or 'press_key' for scrolling.

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