Get crawl errors

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that results are paginated, which is useful beyond the annotations, but says nothing about ordering, error fields returned, or whether pagination is cursor-only. With annotations carrying the safety profile, a 3 fits.

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 front-loaded sentence with no filler, which is appropriate for a simple list tool. The brevity is efficient rather than padded, though one more clause on pagination or attemptId would have paid for itself.

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 and zero schema description coverage across four parameters, so the description is the only place attemptId and cursor semantics could be explained — and it is silent on both. For a paginated error-listing tool an agent will likely misuse or omit attemptId on the first call.

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 0%, so the description must carry the parameter burden. It explains 'id' (task id) and hints at pagination via 'paginated', but 'attemptId' is never mentioned and 'limit'/'cursor' get no syntax or bounds (1-1000 maximum) beyond the raw schema types.

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?

Specific verb and resource: 'Read a paginated list of crawl errors by task id.' It clearly scopes to crawl tasks, which separates it from get_batch_errors and get_crawl_pages without naming them. It stops short of explicit sibling differentiation, but the resource is unambiguous.

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 phrase 'by task id' implies a prerequisite crawl task but states no conditions for when to call this versus get_crawl, wait_crawl, or get_crawl_pages. No alternatives or exclusions are named, leaving the agent to infer the intended situation.

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