Seo Api2 MCP Server

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

With no annotations provided, the description carries full responsibility for behavioral disclosure but provides none. It doesn't indicate whether this is a read-only operation, what kind of data it returns, whether it has rate limits, authentication requirements, or any side effects. The description is completely silent on behavioral traits.

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?

While technically concise with just three words, this is a case of under-specification rather than effective conciseness. The description doesn't provide enough information to be useful, failing to front-load essential purpose or usage information. Every word should earn its place, but here the words don't provide meaningful value.

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 a tool with 5 parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool returns, how it behaves, or even what it fundamentally does. For a tool that presumably checks keyword rankings (inferred from name only), this minimal description fails to provide the necessary context for effective use.

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 5 parameters with descriptions. The description adds no additional meaning about parameters beyond what's in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 'Keyword Rank Checker' is a tautology that merely restates the tool name without explaining what the tool actually does. It provides no verb or specific action, no indication of what resource it operates on, and no differentiation from sibling tools like 'serp_api' or 'keywords_suggestion_tool' that might have related functionality.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, appropriate contexts, or exclusions, nor does it reference any sibling tools for comparison. This leaves the agent with no usage context beyond what can be inferred from the name alone.

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