Audits content quality, search intent classification (Informational, Commercial, Transactional, Navigational), thin content risks, readability, and E-E-A-T signals.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | Target file path or live URL. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It does disclose what dimensions are assessed, such as intent classification and E-E-A-T signals, which is useful behavioral context. However, it does not mention side effects, permissions, rate limits, or whether the operation is read-only, leaving some behavioral ambiguity.
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 information-dense sentence with no filler. Each listed audit dimension adds meaningful scope, and the structure fronts the main action clearly.
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 one parameter and no output schema, the description lists what will be audited in reasonable detail, which helps an agent understand the tool's scope. However, it does not describe what the returned report looks like or how results are structured, and with no annotations or output schema the description could do more to fully prepare the agent.
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%: the only parameter, 'target', is already described as 'Target file path or live URL.' The description does not add further semantic detail about the parameter, so the schema carries the heavy lifting.
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 uses a specific verb ('Audits') and a clear resource ('content quality') while naming concrete dimensions: search intent classification, thin content risks, readability, and E-E-A-T signals. It distinguishes itself from siblings like seo_audit_technical or seo_audit_onpage by focusing on content, though it does not explicitly contrast itself with them.
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 gives no guidance on when to choose this tool over alternatives. Siblings like seo_audit_onpage and seo_audit_technical may overlap in scope, but no explicit when-to-use or when-not-to-use guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most audit tools target distinct SEO dimensions, but several overlap: seo_audit_technical, seo_audit_robots_and_sitemap, and seo_audit_sitemap_multipage all involve robots.txt, sitemaps, and header checks. The descriptions help, but an agent could easily misselect between these related tools.
All tools follow a consistent seo_ prefix with clear verb_noun snake_case naming: audit_, crawl_, discover_, generate_, suggest_, test_, validate_. There is no mixing of conventions or vague generic verbs.
With 21 tools, the server sits in the 16-25 'heavy' range. The broad SEO scope justifies many of them, but the large number of overlapping audit variants makes the set feel slightly bloated.
The server covers the SEO lifecycle well: discovery, crawling, dimension-specific audits, full audits, code fixes, sitemap/robots generation, and validation. Minor gaps such as dedicated backlink or mobile usability audits exist, and the '8-dimension' full audit claim does not align with the 12 distinct audit tools.