scrape_current_view

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one meaningful trait — that no scrolling occurs, so results are limited to currently rendered items and no pagination happens. It says nothing about authentication, rate limits, or which page types it operates on.

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?

A single sentence with no wasted words, and the key constraint ('currently visible ... without scrolling') is front-loaded. Nothing to trim.

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 zero-parameter, no-output-schema tool, the description is nearly sufficient: it tells the agent what it captures and its viewport limitation. It could go slightly further by indicating which page contexts it applies to, but nothing critical is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading or missing parameter information exists.

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?

States a specific verb (scrape) and resource (tweets currently visible on the page) plus a scope qualifier (without scrolling). This distinguishes it from siblings like scrape_timeline and scrape_search_results, which target specific pages, by signaling it grabs whatever is rendered on the current page. It does not, however, name those siblings explicitly.

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?

Usage is only implied: the phrase 'without scrolling' suggests you reach for this when you want a snapshot of the viewport rather than a paginated crawl. There is no explicit statement of when to prefer this over scrape_timeline, scrape_bookmarks, or scrape_thread, nor any prerequisite about which page must be open.

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