Get crawl status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the bar is low. The description adds only that the read is keyed by taskId and returns counters for collapsed/refused links; it discloses nothing about staleness, caching, or behavior for an unknown id.

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?

A single tight sentence with the keyed lookup front-loaded and no filler. It is dense but every clause names a distinct returned datum, so nothing is wasted.

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?

A one-parameter read tool with full schema coverage, complete annotations, and an output schema that already defines the return shape. The description adds the useful framing that this is the report view of a crawl, and nothing an agent needs to call it correctly is missing.

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?

One parameter with 100% schema description coverage ('taskId from crawl'), so the schema already carries the meaning and baseline is 3. The description restates 'by its taskId' but adds no format, source, or lookup guidance beyond the schema.

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?

States a specific verb (Read) and resource (a crawl's report) plus what the report contains: status, page counts, and discovery counters. It is distinguishable from get_crawl_pages, get_crawl_errors, and wait_crawl by describing the report's contents, though it never names those siblings explicitly.

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?

Usage is only implied: the agent gathers it should call this with a taskId to inspect a crawl. There is no statement of when to prefer this over wait_crawl (blocking) or get_crawl_pages/get_crawl_errors, so routing among the crawl-read siblings is left to inference.

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