Crawl Results

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

Annotations already mark the tool as read-only, open-world, and non-destructive, and the description adds important behavioral details beyond them: context overflow limits, a roughly 50 KB response cap, page splitting with contentPart ranges, and cursor-based pagination. It also explains that a missing nextCursor means all pages have been returned, which is exactly the kind of return behavior an agent 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?

The description is front-loaded with purpose and timing, then adds only necessary pagination and alternative guidance. Despite covering several behaviors, every sentence contributes to correct invocation.

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?

There is no output schema, but the description sufficiently explains what is returned, how long pages are handled, and how to retrieve all results. Combined with annotations that cover safety, it is complete for correct use.

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 coverage is 100%, so the schema already documents all three parameters. The description still adds meaningful semantics by explaining the pagination flow for cursor/nextCursor and how limit interacts with the 50 KB response cap and split-page behavior.

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 verb and resource: return crawled pages as Markdown from a crawl started with crawl_start. It distinguishes this from crawl_start, crawl_status, and the precise-work alternative map plus scrape_as_markdown, so an agent can identify its role without opening sibling schemas.

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?

It explicitly says to call this once crawl_status reports the crawl is no longer pending, and it names the alternative for precise work: map plus scrape_as_markdown on the needed pages. This gives clear when-to-use, prerequisite, and alternative guidance.

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