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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to repeat safety. It adds 'synchronously' and a hint about cursor-based pagination, which are useful behavioral details not covered by annotations. However, it omits other behavioral aspects like rate limits, response format, or failure semantics, so it adds only moderate value.

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 short and front-loads the main purpose, but the middle sentence 'Accepts a URLs' contains a grammar error and adds redundancy. It could be tightened to two clear sentences. It is not excessively long, but the structure is slightly awkward.

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 absence of an output schema, the description does not clarify what the returned list contains (e.g., page content, extracted data, links). It also does not explain how waitFor and scanFullPage affect results or mention any prerequisites. For an agent to confidently call this tool, this is a notable gap.

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?

The schema descriptions for url, waitFor, and scanFullPage are already comprehensive, covering usage, constraints, and defaults. The description adds no parameter-specific information beyond reiterating that it accepts URLs. With 100% schema coverage, the baseline is 3, and the description does not exceed that.

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 states a specific action (crawl) and resource (web pages), and notes it works on a small set synchronously. It gives enough for an agent to distinguish it from search or extraction tools, though 'crawl' itself is somewhat vague about whether it returns page content or links. The verb and target are clear.

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 guidance is provided on when to use this tool versus alternatives like web_extract_run or web_search_run. There is no mention of scenarios that favor this tool or exclusions, leaving the agent to infer usage from the name and schema. This is a significant gap given the many sibling web tools.

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