browser_fetch

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

With no annotations provided, the description carries the full burden. It mentions using a 'real headless browser' but does not disclose behavioral traits such as execution time, resource usage, error handling, or side effects. This leaves significant gaps in transparency.

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 a single sentence that is concise and front-loaded with the main action. It is efficient but could include a bit more detail without being verbose.

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?

Given the complexity of a headless browser tool and the existence of an output schema, the description covers the key differentiator from siblings. However, it omits information about error conditions, limitations, and parameter details, leaving it insufficient for complete context.

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 0%, so the description must compensate. It does not explain the purpose or constraints of the 'max_chars' parameter, and only indirectly references the 'url' parameter by mentioning it. No additional semantic value is added beyond the schema.

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 tool renders a URL in a headless browser and returns visible text, including JS-rendered content. It distinguishes itself from the sibling 'web_fetch' by noting that web_fetch cannot see JS-rendered content, so the purpose is specific and well-differentiated.

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?

The description implies usage for pages with JS-rendered content that web_fetch cannot access, providing clear context. However, it does not explicitly state when not to use it or mention alternatives beyond web_fetch, so slightly lacking in complete guidelines.

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