Google Search Console MCP

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

No annotations provided, so description carries full burden. While it adds useful context about domain properties covering subdomains, it fails to disclose safety profile (read-only vs destructive), output format/structure, error handling for invalid URLs, or rate limiting behavior.

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?

Efficiently structured with clear purpose statement followed by Args section. No redundant text. Information density is high with specific examples and constraints included without verbosity.

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?

Adequate for a 2-parameter tool, but gaps remain. No output schema exists, yet description does not hint at return value structure (list of issues, categories, or status codes), which would help the agent process results. Missing safety annotations also leave behavioral gaps.

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?

Excellent compensation for 0% schema description coverage. Clarifies site_url format with examples ('https://...' vs 'sc-domain:...'), specifies exact source requirement (list_properties), and explains the 'one per line' format for the urls parameter. Also documents domain property behavior.

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 specific action ('Check') and resource ('indexing issues') with clear scope ('across multiple URLs'). Differentiates from siblings like inspect_url_enhanced (single URL) and batch_url_inspection (general inspection) by focusing specifically on 'indexing issues' rather than general URL 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?

Provides prerequisite workflow guidance by specifying site_url must come from list_properties. However, lacks explicit when-to-use guidance versus similar siblings (batch_url_inspection) and does not specify when not to use it (e.g., for non-indexing issues or single URL checks).

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