crawl_website

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention rate limiting, permissions, robots.txt compliance, or the format of returned 'structured page content'. This leaves significant gaps for an agent deciding whether to invoke the 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?

Two sentences plus a parameter list are efficient and front-loaded with purpose. The formatting is slightly informal (using 'Parameters:' block), but no unnecessary text. Could be more structured but remains concise.

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 the presence of an output schema, return values are not required. However, the description lacks context on how crawling works (e.g., does it follow sitemap links only? How are max_pages applied?). Additional details on expected behavior and limitations would improve completeness for a complex operation.

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 briefly explains url as 'Website URL to crawl' and max_pages with its default, adding minimal context beyond the schema. This meets a baseline but offers no deeper semantics (e.g., accepted URL formats, page count limits).

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 crawls a website's sitemap and returns structured page content. The verb 'crawl' and resource 'sitemap' are specific and distinct from siblings like 'web_scrape' and 'read_url'.

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 implies use for crawling multiple pages via sitemap, but provides no explicit guidance on when to use this tool versus alternatives (e.g., web_scrape for single pages). No when-not-to-use or exclusion criteria are mentioned.

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