Fetch Page

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

The description mentions stealth mode and a 50,000 character truncation, adding some behavioral context. However, it does not disclose error handling, rate limits, authentication needs, or what happens on failure, leaving gaps for an AI agent.

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 two sentences, front-loading the core action and listing key features. Every sentence adds value with no redundant or vague phrasing.

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?

The description covers extraction modes and truncation but omits return format (e.g., plain text, HTML), error scenarios, and guidance on the wait_for parameter. For a tool with an output schema missing, more detail on output and behavior would be beneficial.

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 is 100% (all parameters described), so the baseline is 3. The description adds truncation limit and extraction mode types, but this context is partially redundant with the schema's enum for extract_mode. No additional per-parameter semantics are provided.

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 fetches and extracts content from a web page using Playwright with stealth mode, listing specific extraction modes. This distinguishes it from sibling tools like search_internet, which perform web searches, and execute_python, which runs code.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks explicit context on when to use fetch_page over search_internet or other tools, and does not mention prerequisites or limitations.

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