crawl_url

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

No annotations are provided, so the description carries the full burden. It never says whether this is a read-only fetch, whether it is expensive or rate-limited, whether JS rendering changes cost or accuracy, or whether results are cached — all material facts for a crawling 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?

A single front-loaded sentence with zero filler and the scope constraint stated immediately. It is efficient, though the brevity leaves semantic gaps that belong to other dimensions rather than being a structural flaw.

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?

An output schema exists, so return values need not be explained, but the tool has no annotations and an undocumented boolean parameter. For a crawler that performs three distinct analyses, the description leaves the agent without enough to predict behavior, cost, or when to prefer a sibling.

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 and does not. It says nothing about 'url' format nor about 'render_js' (default false), which is the one parameter with real behavioral consequences — an agent gets no hint that enabling it trades latency for JS-rendered content.

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?

States a specific verb ('Extract') and resource scope ('a single URL') plus the payload categories (content, technical SEO, GEO intelligence). 'Single URL' implicitly separates it from crawl_domain, but it does not distinguish itself from the overlapping siblings extract_page_content, analyze_seo, and analyze_geo.

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?

No when-to-use guidance, no exclusions, and no named alternatives despite six closely related siblings (analyze_seo, analyze_geo, extract_page_content) that appear to do subsets of this work. The agent must infer whether to call this composite tool or the narrower ones.

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