Google Search Console MCP

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

With no annotations provided, description carries full burden. It discloses key limits (max 500 rows) and pagination constraints (referring to advanced tool), plus default behaviors. However, lacks disclosure of read-only nature, rate limits, error behaviors, or return data structure.

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?

Uses Args: structure which is information-dense but readable. Every line adds value (defaults, constraints, alternatives). Single-sentence purpose statement is front-loaded. Minor verbosity in site_url description is justified by complexity of domain vs URL properties.

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?

Thorough on inputs and limits, but lacks description of return values (clicks, impressions, CTR, position) given no output schema exists. For an analytics retrieval tool, this omission leaves the agent uncertain about the data structure returned.

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 has 0% description coverage. Description fully compensates by documenting all 4 parameters with formats (e.g., 'sc-domain:example.com'), valid options (dimensions list), syntax ('comma' separation), and value ranges (max 500). Exceptional compensation for schema deficiency.

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 verb ('Get') and resource ('search analytics data') with scope ('for a specific property'). Clear what the tool retrieves, though differentiation from siblings like 'get_performance_overview' or 'get_search_by_page_query' is not explicit upfront.

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?

Excellent guidance including explicit alternative ('For bulk exports beyond 500 rows, use get_advanced_search_analytics'), parameter-specific usage recommendations ('Use 5-20 for quick overviews'), and workflow context ('site_url from list_properties').

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