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

Annotations already establish read-only and idempotent behavior. The description adds useful context by specifying the 90-day time window for clicks and that other fields come from the latest completed crawl, which implies a dependency on crawl completion. It does not contradict the annotations.

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 a single 31-word sentence with no filler; the core action is front-loaded before the metric list. It is efficient but slightly run-on, so it falls just short of a perfect structure score.

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?

For a read-only list tool with fully documented parameters and no output schema, the description covers the main return fields and data provenance (90-day clicks, latest crawl). It lacks explicit handling of pagination or what 'issues per page' counts, but these are minor gaps given the schema already documents limits.

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%: site_id, sort, and limit all have descriptive text including defaults and ranges. The description adds no parameter-specific guidance beyond the schema, so it stays at the baseline of 3.

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 names a specific action ('List the pages of a website') and enumerates the exact data returned (Google clicks over 90 days, status code, title, H1, meta description, issues). This makes it clearly distinguishable from sibling tools like get_keywords or list_issues, which target different resources or metrics.

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 description does not explicitly state when to prefer this tool over alternatives or mention related tools such as list_issues or get_site_metrics. However, the detailed output list implies the use case of retrieving per-page SEO and crawl metrics, so the usage is indirectly inferable rather than absent or misleading.

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