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

No annotations are provided, so the description carries the full behavioral burden and delivers none of it. It doesn't disclose whether crawling is long-running or async, whether it respects robots.txt or requires auth, rate limits, or whether an audit mutates state. Only the verb 'crawl' faintly hints at scope/expense.

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 single sentence is front-loaded and free of filler, which is good. But it is undersized for a tool with 17 distinct operations and a deeply nested payload schema, so the brevity comes at the cost of missing essential detail rather than being appropriately economical.

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 high-complexity tool with no annotations and a nested multi-field payload, one sentence is far too thin. The existing output schema reduces the need to describe return values, but nothing in the description helps the agent select an operation or understand crawl scope, so the definition is incomplete for its 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% (only the operation enum has an inline description), and the description adds nothing about any parameter. Critical nested fields like filters, order_by, page_url, max_crawl_pages, enable_javascript, and response_mode are left entirely to the raw schema, and the 17 operation semantics are undocumented.

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 names a clear verb pair (crawl/inspect) and resource (website) with a stated goal (technical and content issues). However, it offers no differentiation from heavily overlapping siblings such as site-map, page-extract, content-analysis, and domain-intelligence, so an agent cannot tell which tool to pick from the description alone.

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?

There is no when-to-use guidance, no mention of prerequisites, and no pointer to alternatives. The 17-value operation enum (summary, pages, links, lighthouse, screenshot, etc.) is never explained, so the agent gets no help deciding which operation addresses its task.

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