scroll_to_element

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

No annotations provided. The description implies repeated scrolling until visibility, but does not disclose behavior like auto-stopping criteria, timeout, or side effects. Lacks details on what happens if element is not found.

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?

Single sentence, front-loaded with action. Efficient but slightly vague. No extraneous content, but could be more precise.

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?

For a simple tool with no output schema and siblings like 'scroll', the description lacks needed context. It does not explain the format of 'elementPath' or scroll behavior. Incomplete for effective selection.

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 coverage is 100%. The parameter descriptions are adequate but the tool's description introduces 'text or role' which does not correspond to the provided parameters, causing a mismatch. The description adds minimal value beyond schema.

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 until a UI element becomes visible. The verb 'scrolls' and resource 'UI element' are clear. However, it mentions 'text or role' which are not reflected in the input schema, causing some confusion.

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 siblings like 'scroll'. No conditions or alternatives mentioned. The description is too brief to differentiate usage context.

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