crawl

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

No annotations are provided, so the description carries the transparency burden. It discloses the key behavior (headless Chromium rendering, returning full rendered HTML), which goes beyond the tool name. It doesn't mention potential limitations like timeouts or failures, but for a simple single-parameter tool this is adequate.

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 two sentences, front-loaded with the core function, and each sentence earns its place. There is no fluff or repetition of schema information.

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?

For a simple tool with one parameter and an output schema, the description covers the essential 'what' and 'when' without needing to explain return values (handled by output schema). It's complete enough for an agent to select and invoke correctly, though it could mention edge cases.

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?

With schema description coverage at 0% and one parameter (url), the description fails to add any meaning about the parameter. It doesn't explain the URL format, required protocols, or behavior for invalid URLs, leaving the agent to infer from the tool's name and function.

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 explicitly states the tool renders a page with headless Chromium and returns full rendered HTML, using a specific verb and resource. It also distinguishes from siblings by noting the SPA/client-side rendering use case, which differentiates it from fetch_page and crawl_site.

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 provides a clear 'when to use' condition ('when the page is a SPA or uses client-side rendering'), implying the alternative (non-SPA) case. However, it does not explicitly name alternative tools or give when-not-to-use guidance, so it stops short of full explicitness.

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