scrape_bookmarks

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the automatic navigation behavior (implying no prior navigation step is required), but says nothing about login/auth requirements, whether it scrolls, or what happens on failure — significant gaps for a scraper tool.

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 short sentences, front-loaded with the core action, and the second sentence adds the key navigation behavior. No wasted words.

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 single-parameter scraping tool with no output schema, the description covers purpose and the auto-navigation behavior, which is the main ambiguity versus the separate navigate_to_bookmarks sibling. It would be stronger with a hint about the returned content and auth prerequisites.

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?

Only one parameter ('limit') and schema description coverage is 100%, so the schema already documents it fully. The description adds no semantics about how limit is applied (e.g., truncation behavior or whether it stops scrolling). Baseline 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?

States a specific verb and resource ('scrape bookmarked tweets from Twitter/X'), which cleanly separates it from scrape_timeline, scrape_search_results, and scrape_current_view. It does not, however, explicitly name which sibling it replaces or why an agent would pick it over 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 note that it 'automatically navigates to the bookmarks page' implies the tool is self-contained and does not need navigate_to_bookmarks first, which is useful. But there is no explicit when-to-use/when-not-to-use guidance or stated alternative for scraping bookmarks.

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