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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds the meaningful behavioral context that results are paged and that issue rule_ids are grouped by finding class, plus where the rule_id input comes from. It does not explain pagination termination or result sizing, keeping it below a 5.

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?

Front-loads what is returned, then covers the two main filtering modes and the sibling relationship in two dense sentences. Every sentence carries information, though the phrasing is compressed to the point of being slightly terse.

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?

With no output schema, the description usefully enumerates the shape of each returned page and explains the paging model, which is the key gap. A 7-parameter tool at 43% schema coverage could still say more about pagination limits and cursor lifecycle.

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 43%; the description explains the intent of rule_id (duplicating the schema) and gives loose semantics for page_kind/status filters, but adds nothing for limit, and only implicitly touches cursor/crawl_id. It partially compensates for the coverage gap rather than closing it.

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+resource ('Pages from a crawl') and enumerates the returned fields (URL, title, page type, status, scores, issue count, rule ids by finding class). It also explicitly differentiates itself from sibling read_site_health as the totals view.

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?

Gives clear usage conditions: pass rule_id (sourced from read_site_health top_issues or an issue group) to list pages affected by an issue, and filter by page_kind/status to find pages by type or status. It names the relationship to read_site_health but stops short of explicit when-not-to-use guidance.

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