SEO Analytics MCP

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

With no annotations, the description carries full burden but only states the merge action without behavioral details. It doesn't disclose whether this is read-only or mutative, authentication needs, rate limits, data processing time, or error handling. The term 'merge' suggests data transformation but lacks operational context.

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 a single, efficient sentence with zero waste, front-loading the core purpose. It's appropriately sized for a tool with an output schema, avoiding unnecessary elaboration.

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 6 parameters with 0% schema coverage, no annotations, and an output schema, the description is incomplete. It covers the high-level purpose but lacks details on parameters, behavioral traits, and usage context. The output schema mitigates some gaps, but overall completeness is minimal.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'site_url', 'property_id', or other parameters mean, their relationships, or how they affect the merge. The baseline is low due to poor coverage and no compensation.

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 ('merge') and resources ('normalized GSC + GA4 page metrics'), specifying the outcome ('into one dataset'). It distinguishes from siblings by focusing on data merging rather than reporting, analysis, or raw queries, though it doesn't explicitly name alternatives.

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 on when to use this tool versus alternatives like analytics_trend_report or gsc_query_page_pairs is provided. The description implies usage for combining metrics but lacks context on prerequisites, data availability, or specific scenarios where merging is preferred over separate queries.

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