html

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'rendered' HTML, which hints at browser rendering, but does not disclose side effects, redirect handling, authentication needs, rate limits, or output formatting. This is insufficient for a network-fetching tool.

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, front-loaded sentence with no wasted words. It conveys the core purpose efficiently and is easy to parse.

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 that the tool has three parameters (including complex config objects), no output schema, and no annotations, the description is incomplete. It does not explain what 'rendered' means in practice, what the browser_config/crawler_config options do, or the structure of the returned HTML. The description is too minimal for the tool's complexity.

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 only implies the 'url' parameter by saying 'for a URL', but does not explain 'browser_config' or 'crawler_config' at all. The description adds little value beyond the schema's field names and defaults.

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's function: 'Fetch rendered HTML for a URL.' It uses a specific verb ('fetch'), a specific resource ('rendered HTML'), and a target ('URL'). This distinguishes it from sibling tools like 'screenshot', 'pdf', 'md', and 'extract' by the output format.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios, exclusions, or relations to sibling tools such as 'md' (markdown) or 'screenshot'. Users are left without context for choosing this tool over others.

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