webclaw

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

No annotations provided, so description carries full disclosure burden. Adds valuable operational context about automatic fallback to webclaw cloud API for bot protection and JS rendering, but omits rate limits, authentication requirements, timeout behavior, and error handling.

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 with zero waste. First sentence establishes core functionality and output options; second provides critical implementation detail about fallback behavior. Well-structured and appropriately front-loaded.

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?

Adequate for a 6-parameter tool with complete schema coverage. Description compensates for missing output schema by detailing return format options, though could enhance with error behavior or rate limit documentation given the web scraping domain.

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 has 100% description coverage (baseline 3). Description adds semantic value by clarifying that 'llm' format means 'LLM-optimized text' and elaborating on format intentions beyond the schema's terse descriptions.

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?

Clear specific verb 'scrape' with scope 'single URL' that explicitly distinguishes from sibling tools like 'batch' and 'crawl'. Lists output formats (markdown, LLM-optimized text, plain text, JSON) to clarify extraction capabilities.

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?

Implicitly differentiates from batch/crawl via 'single URL' phrasing, but lacks explicit when-to-use guidance versus siblings like 'extract' or 'map'. No mention of prerequisites such as URL accessibility or when to prefer local vs cloud fallback.

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