mcp-seo-audit

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

With no annotations, the description carries full burden but lacks behavioral details. It mentions 'submit or resubmit' but doesn't disclose whether this requires authentication, has rate limits, affects indexing status, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 description is front-loaded with the core purpose, followed by clear parameter explanations in a structured 'Args:' section. Every sentence earns its place with no wasted words, making it efficient and easy to parse.

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?

Given 2 parameters with no schema descriptions, the description adequately explains parameter semantics, and an output schema exists (so return values needn't be described). However, as a mutation tool with no annotations, it lacks behavioral context like side effects or error handling, leaving gaps in completeness.

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 description coverage is 0%, but the description compensates by explaining both parameters: 'site_url' as the 'Exact GSC property URL' and 'sitemap_url' as the 'Full URL of the sitemap to submit'. This adds crucial meaning beyond the bare schema, though it doesn't cover format examples or validation rules.

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 clearly states the action ('submit or resubmit') and target resource ('a sitemap to Google'), making the purpose unambiguous. It distinguishes from siblings like 'get_sitemaps' (read) and 'delete_sitemap' (remove), but doesn't explicitly differentiate from 'add_site' or other submission-related tools, keeping it at 4 rather than 5.

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?

No guidance is provided on when to use this tool versus alternatives like 'batch_request_indexing' or 'request_indexing', nor any prerequisites (e.g., site verification in Google Search Console). The description implies usage for sitemap submission but offers no context about timing, frequency, or constraints.

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