scrape_page

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

With no annotations, the description carries full burden. It explains extraction behavior, format options, content stripping, link inclusion, render modes, and timeout. It does not cover side effects or error conditions, but the core behavior is well disclosed.

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?

The description is a multi-line docstring with an Args block. It is well-structured and front-loaded with the purpose. While it is somewhat verbose for 6 params, each sentence is necessary, and there is no wasted text.

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 6 parameters, no output schema, and no annotations, the description covers all aspects: what the tool does, each parameter's purpose and default, and return type. It is complete for an agent to select and use correctly.

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 0%, so the description fully explains all 6 parameters: url, format with default, main_content, include_links, render with options (auto/http/browser), and timeout_ms. Each parameter's role is clear, adding meaning beyond the schema.

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 the action ('scrape a single URL'), the resource ('URL'), and the output ('return extracted content'). It also notes 'no browser session needed', distinguishing it from browser-based tools like browser_navigate.

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 when to use (single page, no browser) and provides render options ('http' cheapest, 'browser' full render) to guide choice. However, it does not explicitly state when not to use or point to specific sibling alternatives.

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