Fetch Page

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

With no annotations, the description carries the burden and does well: it discloses the rendering backend, pagination model, the arXiv routing and its rate-limit implications, the `source` provenance field, and the exact failure shape. It omits auth/rate-limit behavior for non-arXiv sites and timeout characteristics.

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?

Front-loads the core action in the first sentence and then layers pagination, routing, provenance, and error contract. Dense but nearly every clause adds callable information; minor overlap between the pagination and source-provenance sentences.

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?

An output schema exists, so return values need not be fully described, and the description covers the pagination and error cases that matter. A note on non-arXiv fetch limits or timeouts would complete it, but nothing essential to a correct call is missing.

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 0%, so the description must compensate, and it explains the offset/max_chars slice semantics and continuation pattern clearly, plus the url-dependent arXiv routing. It does not state the default values (0, 20000) or units, but the slice notation conveys enough to call correctly.

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?

States a specific verb+resource: fetch a web page as markdown, rendered via headless Chromium. This implicitly distinguishes it from fetch_stealth/fetch_pdf (JS rendering, markdown output), though no sibling is named explicitly.

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?

Gives clear operational guidance for continuing pagination ('call again with a larger offset') and for arXiv URLs (alphaxiv default, browser fallback). However, it offers no guidance on when to choose this tool over fetch_stealth, fetch_pdf, or web_search.

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