read_page

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

Discloses key behaviors: JavaScript rendering, robots.txt compliance, automatic trial key creation, and refusal to bypass blocked sites. No annotations exist, so description carries full burden well.

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?

Well-structured with main description followed by parameter details. Some redundancy (e.g., 'optional' repeated) but overall efficient and easy to parse.

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?

Covers return format (clean markdown, metadata), auth behavior, and JS handling. Missing specifics on error scenarios or limitations, but adequate for typical use.

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 coverage 0%, but description explains each parameter's purpose (url required, api_key optional with auto-creation, wait_for_selector for CSS selector, scroll for lazy content). Adds significant meaning.

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?

Clearly states it loads a web page and returns clean markdown with metadata, differentiating from siblings like screenshot, pdf, register, and balance by focusing on text content extraction.

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?

Provides context for use: handles JavaScript, respects robots.txt, and explains optional parameters. Lacks explicit when-not-to-use or alternatives, but sibling tools are distinct.

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