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

With no annotations, the description must carry the full behavioral burden. The verb 'inspects' implies a read-only audit and the description lists concrete checks, but it does not mention whether live network requests are made, whether authentication is needed, what kind of output is returned, or any rate/time implications.

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 audit targets in a readable list. The word 'Deeply' adds little value, but overall the structure is compact and easy to parse.

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 single-parameter audit tool, the description covers a broad and clear functional scope: robots rules, sitemap validity, sitemap/robots conflicts, and security headers. It lacks output format details and usage differentiation, but given the tool's simplicity, it is reasonably complete.

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?

The input schema already fully documents the single 'target' parameter, including both URL and local folder path options. The tool description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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 specifies what the tool inspects: robots.txt allow/disallow rules per user-agent, sitemap.xml validity, disallowed pages appearing in sitemaps, and HTTP security headers. It is specific about the resource and scope, though it does not explicitly differentiate itself from overlapping siblings like seo_audit_sitemap_multipage or seo_audit_technical.

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?

There is no guidance on when to use this tool versus alternatives. The description implies it is for robots.txt and sitemap auditing, but it never states when not to use it or names sibling tools that cover partially overlapping concerns.

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