scrape_search_results

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It discloses that the tool navigates to a search page, but it omits return format, pagination behavior, rate limits, authentication requirements, and whether the scrape is read-only or has side 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?

Two sentences, front-loaded with the core action and followed by the navigation detail. Both sentences earn their place and contain no filler.

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 two-parameter scrape tool with no output schema and no annotations, the description covers the basic action but not the return shape or how 'limit' affects pagination. It is adequate but leaves an agent guessing about the output structure.

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 already documents both parameters ('query' and 'limit'). The description mentions the given query but adds no syntax, constraints, or meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource: 'Search for tweets and scrape the results.' It also clarifies the mechanism ('Navigates to search page with the given query'), which distinguishes it from sibling scrape tools like scrape_timeline, scrape_bookmarks, and scrape_current_view.

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?

The description implies the tool is used to search tweets, but it gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as navigate_to_search or scrape_timeline, nor does it state prerequisites like authentication.

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