Google Search Console MCP

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

No annotations are provided, so the description carries the full disclosure burden. While 'Delete (unsubmit)' implies a destructive operation, the description fails to disclose side effects (impact on indexing), reversibility, required permissions/verification levels, or error conditions.

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 structure is effective with a clear one-sentence summary followed by an Args breakdown. Information is front-loaded. The domain property explanation adds slight verbosity but provides valuable context. 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?

For a two-parameter deletion tool with no output schema, the description adequately covers input requirements. However, it lacks disclosure of return values (success indication), error scenarios, or whether the operation affects historical GSC data associated with the sitemap.

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 Args section provides substantial compensation: site_url includes format examples (https:// vs sc-domain:), source reference (list_properties), and domain property behavior notes. Sitemap_url clarifies it expects the 'full URL'. Minor gap: no format validation details for sitemap_url.

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 opens with a specific verb ('Delete') and clarifies with synonym ('unsubmit'), targeting a specific resource (sitemap) in a specific system (Google Search Console). This clearly distinguishes it from sibling tools like get_sitemaps, submit_sitemap, or manage_sitemaps.

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?

The description provides prerequisite context by specifying that site_url must come from list_properties and explaining domain property formats. However, it lacks explicit guidance on when to use this versus the manage_sitemaps sibling or warnings about verification requirements.

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