fetch_page

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

No annotations are provided, so the description must fully disclose behavior. It mentions Chromium headless browser (implying resource usage) but does not cover side effects, authentication needs, rate limits, or what happens to the browser instance after use. This is insufficient for a tool with no annotations.

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 sentences are concise and front-load the core action and utility. No unnecessary information, though a slightly more structured format (e.g., mentioning intended use) could improve readability.

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 hints at return format and browser usage but lacks details on error behavior, timeouts beyond parameter, or handling of network failures. Given no output schema, more completeness 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%, so the schema already documents all 4 parameters well. The description adds minimal value beyond confirming output format ('markdown' or 'html'), which is already in the schema. Baseline score of 3 is appropriate.

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 a web page using Chromium and returns content in markdown or HTML, with specific mention of dynamic sites requiring JavaScript rendering. It distinguishes from siblings like screenshot or interact, but does not explicitly contrast with them.

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 indicates usefulness for dynamic sites but lacks explicit when-not-to-use guidance or comparison with sibling tools (e.g., when to use fetch_page vs extract_data). No exclusions or prerequisites are mentioned.

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