Ahrefs 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. It mentions the tool performs analysis but doesn't describe what happens during execution (e.g., is it synchronous/asynchronous, does it make external API calls, are there rate limits, what permissions are required, what happens on failure). The description is minimal and lacks essential behavioral context for a tool with 5 parameters.

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 reasonably concise with two sentences, but the second sentence about using the 'doc tool' feels like a workaround rather than essential information. The first sentence is front-loaded with the core purpose, but overall structure could be improved by integrating parameter guidance more naturally.

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 tool with 5 parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It provides basic purpose but lacks essential details about parameter meanings, behavioral characteristics, output format, and differentiation from similar tools. The mention of using 'doc tool' suggests incomplete documentation that requires external reference.

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 schema provides no parameter documentation. The description mentions 'selected SEO, backlink, organic, and paid traffic metrics' which hints at the 'select' parameter's purpose, and 'multiple URLs, domains, or subdomains' hints at 'targets'. However, it doesn't explain 'country', 'order_by', or 'volume_mode' parameters at all, leaving 3 of 5 parameters completely undocumented.

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 performs 'batch analysis of multiple URLs, domains, or subdomains' to retrieve specific SEO and traffic metrics. It specifies the verb ('performs batch analysis'), resource ('URLs, domains, or subdomains'), and scope ('selected SEO, backlink, organic, and paid traffic metrics'), but doesn't explicitly differentiate from sibling tools like 'site-explorer-metrics' or 'site-explorer-metrics-by-country'.

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. It mentions 'Use doc tool first to get the real input schema' which is a technical prerequisite rather than usage context. There's no indication of when batch analysis is preferred over individual analysis tools or how it differs from similar sibling tools.

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