scroll_to_text

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

With no annotations, the description must carry behavioral disclosure. It usefully states that this drives a real Chrome browser via the OctoLimb extension and should only be used for real website tasks. However, it does not describe what happens when the text is not found, whether scrolling is smooth or instant, or any side effects, leaving some behavioral gaps.

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 short and front-loads the environmental constraint before the usage condition. It contains a minor grammatical typo ('dont') but no wasted sentences, and every part contributes useful context.

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 scroll-to-text action with a fully described input schema and no output schema, the description provides adequate completeness: it names the browser environment, the real-website restriction, and the viewport condition. Nothing essential for correct invocation is missing, though failure behavior remains unstated.

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 100%, so the schema fully documents all three parameters including nth and intent. The description adds no additional parameter-level meaning beyond what the schema already provides, which sets the baseline at 3.

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 a specific action (scroll to text) and its triggering condition (when the target is not visible in the current viewport). It does not explicitly distinguish this tool from sibling scroll tools like scroll_to_percent or scroll_to_top, but the name and description together make the purpose unambiguous.

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?

It gives a clear when-to-use condition: when the desired element is outside the current viewport. The bracketed context also specifies that it should only be used when acting on a real website via the OctoLimb extension. It lacks explicit when-not or alternative scroll-tool guidance, but the context is sufficient.

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