Serpstat MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions what data is returned (keywords with position, traffic, difficulty analysis), it lacks critical behavioral information: whether this is a read-only operation, any rate limits, authentication requirements, data freshness, or pagination behavior (despite having page/size parameters). The description doesn't contradict annotations since none exist, but it's insufficient for a complex 11-parameter tool.

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 that front-loads the core purpose. Every element ('Get keywords that domain ranks for', 'Google search results', 'position, traffic, difficulty analysis', 'comprehensive SEO insights and performance metrics') contributes meaning without redundancy. However, it could be slightly more structured by separating core function from included metrics.

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 complex tool with 11 parameters, nested objects, no annotations, and no output schema, the description is inadequate. It doesn't explain the relationship between parameters (e.g., how filters interact with keywords arrays), doesn't describe the return format despite rich filtering capabilities, and provides no behavioral context. The description fails to compensate for the lack of structured metadata about this sophisticated analysis tool.

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 100%, so the schema already documents all 11 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema descriptions. It mentions 'comprehensive SEO insights and performance metrics' which aligns with the detailed filter and sort parameters, but provides no additional semantic context about parameter usage or relationships.

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 tool's purpose: 'Get keywords that domain ranks for in Google search results' with specific details about included metrics (position, traffic, difficulty analysis, SEO insights, performance metrics). It distinguishes from siblings like 'get_keywords' by focusing on domain-specific ranking analysis, though it doesn't explicitly compare to alternatives like 'get_domain_uniq_keywords'.

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 no guidance on when to use this tool versus alternatives. With many sibling tools for keyword and domain analysis (e.g., 'get_keywords', 'get_domain_uniq_keywords', 'get_url_keywords'), there's no indication of when this specific domain-focused keyword ranking tool is preferred over other keyword-related tools.

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