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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds valuable context beyond that: ~10–20 second runtime, nothing is stored, and a paid access-key requirement. It does not mention error or rate-limit behavior, keeping it short of 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-loaded with what it reads and what it returns, then runtime/privacy and the access requirement. The parenthetical list of SEO problems is long but each item is informative; no sentence is pure filler.

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 carries the burden of describing returns and does so — problem list, today's Google snippet plus truncation point, and the fixes the corrector would apply. Only the response shape/structure (counts, fields) remains unspecified.

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 100% and both parameters (url, access_key) are documented in the schema with examples and the 'pass_…' key format. The description adds no format or constraint detail beyond what the schema already supplies, so baseline 3 applies.

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 and resource — reads the public home page and a few sitemap pages the way a search engine does — and enumerates the returned findings (duplicate titles, missing h1, robots.txt, mixed content, etc.). That crawl scope cleanly separates it from the sibling check_ai_crawler_access, which only inspects crawler access.

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 implied (audit a site's SEO health) and a prerequisite is given (connector access pass, €9.90/24h or €29/month). However, there is no explicit when-to-use vs. when-not, and the adjacent tools read_audit_report and get_full_audit_checkout are never contrasted.

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