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. Adds valuable behavioral context about domain properties covering all subdomains and filtering strategy. However, fails to disclose error behavior, authentication requirements, or what specific 'details' are returned.

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?

Well-structured with clear separation between purpose statement and Args section. Information is front-loaded. The subdomain explanation, while specific, earns its place by clarifying a non-obvious usage pattern. No redundant or filler text.

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 single-parameter tool, with good parameter documentation. However, given the lack of output schema, the description should ideally specify what 'detailed information' includes (e.g., verification status, permissions, crawl errors) rather than leaving it completely opaque.

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?

With 0% schema description coverage, the description compensates effectively by specifying the parameter must be 'Exact', providing two format examples ('https://...' and 'sc-domain:...'), and indicating the data source (list_properties). The subdomain filtering note also clarifies usage.

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?

Clear verb ('Get') and resource ('detailed information about a specific Search Console property'). Implicitly distinguishes from sibling 'list_properties' by specifying 'specific' property and referencing list_properties as the source for the URL parameter.

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 implicit workflow guidance by stating the site_url must come from 'list_properties'. Includes useful domain property usage pattern (covering subdomains). However, lacks explicit 'when not to use' or direct comparison to siblings like 'add_site' or 'delete_site'.

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