browserless_smartscraper

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

Annotations already indicate read-only (readOnlyHint: true) and non-destructive (destructiveHint: false). The description adds value by mentioning automatic handling of JavaScript and anti-bot measures. Although it doesn't detail auth profile or timeout behavior, the overall transparency is good.

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, no wasted words. The first sentence clearly states the core functionality and return types; the second provides important alternatives. It is front-loaded and efficient.

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?

Given the well-documented schema and annotations, the description is mostly complete. It covers purpose, alternatives, and key behaviors. However, lacking details about return structure (since no output schema) and edge cases slightly reduces completeness.

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 input schema has 100% coverage with descriptions for all five parameters. The description adds marginal value by mentioning markdown/HTML formats, but the schema already defines formats with defaults. Baseline 3 is appropriate.

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 it scrapes a SINGLE webpage and returns content as markdown or HTML. It explicitly distinguishes from sibling tools 'browserless_crawl' (multiple pages) and 'browserless_map' (list URLs), making 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?

The description provides explicit when-to-use (single page scraping) and when-not-to-use (use crawl for multiple pages, map for listing URLs). It also notes it handles JavaScript-heavy pages and anti-bot measures, guiding proper usage.

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