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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the specific data being checked (indexing, crawl, mobile, rich results) but does not disclose any additional behavioral aspects like rate limits or authentication details. This exceeds the baseline without duplicating 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 short, front-loaded with the core purpose, and the routing instruction is placed after the main description as a separate, clear section. No unnecessary words or repetition.

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 inspection tool with three required parameters and no output schema, the description covers what the tool does, when to use it, and the critical prerequisite for the site_url. The return information is implied by the list of checks. Nothing essential 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?

All parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds extra semantic value by instructing that site_url must be obtained from get_site_list, which clarifies the correct usage of that parameter beyond the schema example. This warrants a 4.

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 clearly states it inspects a URL in Google Search Console and lists the specific checks (indexing status, crawl errors, mobile usability, rich results). This distinguishes it from sibling tools like browse_url or read_web_page, which are about fetching content, not GSC inspection.

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?

Explicitly provides use cases ('technical SEO audits, diagnosing why pages aren't appearing in search, or checking mobile-friendliness') and even includes routing instructions to call get_site_list first, which is a concrete prerequisite. This leaves no ambiguity about when and how to invoke the tool.

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