smart_fetch

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

The description usefully discloses the escalation behavior and the efficiency motive, which is valuable. But it states the browser fires 'ONLY' when anti-bot blocking is detected, while the force_browser parameter can override that behavior, creating a partial mismatch. With no annotations available, it also does not explain side effects, return shape, or failure modes.

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 short and front-loaded with the core mechanism. The second sentence reinforces the efficiency value proposition, but somewhat redundantly restates the 'only when needed' idea from the first sentence.

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?

With five parameters, zero schema descriptions, no output schema, and no annotations, the description alone is not enough to invoke this tool correctly. It explains the strategic behavior but omits return format, parameter defaults/effects, and edge-case behavior.

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% and the description does not explain any parameter, including url, proxy, max_chars, impersonate, or force_browser. The dual-mode narrative implicitly relates to force_browser and impersonate, but the agent is left without actual parameter semantics.

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 what the tool does: it fetches via a dual-mode path, trying browserless HTTP first and escalating to a stealth browser only when anti-bot blocking is detected. It communicates a distinct hybrid behavior, though it does not explicitly contrast itself with sibling tools like http_request or scrape_page.

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?

It gives clear context for when this tool is valuable: high-volume reading where efficiency matters, with the browser used only when necessary. However, it stops short of explicit guidance on when NOT to use it or which sibling tools to prefer in other scenarios.

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