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

No annotations are provided, so the description carries the transparency burden. The word 'audit' and the listed checks suggest a read-only analysis, but the description does not explicitly state that the target is never modified or describe output behavior. It is not contradictory, just thin.

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 front-loaded sentence that states the action first and then lists the audit dimensions compactly. There is no filler or redundant repetition of the tool name.

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?

The tool is low-complexity: one required parameter is fully documented, and the audit scope is explicitly enumerated, so an agent can invoke it with only a target. The absence of output details is a minor gap, especially since no output schema exists.

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 schema already documents the only parameter, 'target', as 'Target file path or live URL' with 100% coverage. The description adds no additional parameter-level meaning, so the baseline 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 uses a clear action and resource: 'Performs On-Page SEO audit' and then enumerates concrete audit areas (title tag, meta description, H1-H6, OpenGraph, Twitter cards). It is clear, but it does not explicitly contrast itself with the many sibling audit tools.

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 implies use when an on-page audit is needed, but it gives no explicit when-to-use or when-not-to-use guidance. With 20 similar seo_audit_* siblings present, an agent gets little help choosing this tool over seo_audit_content or seo_audit_technical.

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