fetch_page

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

With no annotations, the description carries the full behavioral burden. It discloses the primary action and output format, and that tab_id supports persistent sessions. However, it does not clarify side effects such as whether a new tab is opened, whether tabs remain open, or how failures/timeouts behave.

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 concise sentences with no filler. The main purpose is stated first, followed by the session capability. Every word earns its place.

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 plus schema covers parameters and the Markdown output, making simple calls feasible. However, with no annotations, no output schema, and a browser tool that may have side effects, it lacks guidance on tab lifecycle, required input combinations, and when to use alternatives.

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 100%, so the schema already documents all five parameters. The description adds little beyond the schema; 'persistent sessions via tab_id' restates the schema's tab_id description rather than adding new 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?

The description clearly states the action ('Load a URL'), the resource ('URL'), and the result ('full page content as Markdown'). It also mentions persistent sessions via tab_id, which distinguishes it from simpler fetch tools. However, it does not explicitly differentiate itself from sibling tools like fetch_readable or fetch_structured_data.

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?

There is no guidance on when to use fetch_page versus alternatives such as fetch_readable, open_tab, or crawl. The mention of persistent sessions via tab_id is a partial usage hint, but it does not explain when to prefer this tool or when to avoid it.

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