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. Fails to specify what 'detailed information' includes (errors, URL counts, last submission date?), omits read-only safety confirmation, error handling, or rate limits. Only behavioral context added is the domain property coverage note.

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 block format that is information-dense and front-loaded. The domain property explanation, while lengthy, is necessary context. No redundant filler, though the docstring style slightly duplicates schema structure that could have been utilized.

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?

Input parameters are thoroughly documented given the empty schema, but the tool lacks output schema and the description fails to hint at return values (what 'details' are returned?). Acceptable for a simple retrieval tool but gaps remain in describing the response structure.

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. Provides specific format examples for 'site_url' (https://example.com/ vs sc-domain:example.com), specifies the source tool ('list_properties'), and explains domain property behavior. 'sitemap_url' is adequately described as the full URL to inspect.

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 clear verb ('Get') and resource ('detailed information about a specific sitemap'), but does not explicitly differentiate from sibling tool 'get_sitemaps' (likely a list operation) beyond the singular vs plural naming convention.

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 guidance ('Exact GSC property URL from list_properties') and useful domain property context (subdomain handling), but lacks explicit 'when to use this vs alternatives' guidance comparing it to 'get_sitemaps' or 'list_sitemaps_enhanced'.

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