crawl_site

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

Discloses limits (max pages, parallel runs) and output structure, but with no annotations, it could mention more traits like potential slowness or authentication needs.

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?

Three concise sentences: purpose, output, constraints. No wasted words, front-loaded.

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?

Covers purpose, output, and constraints adequately for a tool with few parameters and no output schema. Could include error handling or behavior on missing sitemap.

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 covers all 3 parameters (100% coverage), so description adds little beyond clarifying crawling method for url. Baseline 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?

Description clearly states it discovers all pages via sitemap or crawling and runs Lighthouse, returning per-page and summary results. This distinguishes it from siblings that focus on single pages or comparisons.

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?

Provides context (site-wide audit) and constraints (max 20 pages, 3 parallel runs), but does not explicitly state when to use vs alternatives like analyze_performance for single pages.

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