seo_audit_onpage

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

With no annotations provided, the description carries the full burden, and it explicitly states 'Safe, read-only diagnostic evaluation. No file modifications.' This clearly discloses the tool's non-destructive behavior, which is essential for an agent deciding whether invocation is safe.

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 well-structured with clear sections for purpose, usage guidelines, and behavioral transparency. Every section earns its place, and the most important information is front-loaded in the opening sentence.

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, read-only audit tool, the description covers purpose, usage boundaries, and safety. It does not explicitly describe the output format or return shape, but the absence of an output schema and the simplicity of the tool make this a minor gap rather than a serious omission.

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%, and the only parameter, target, is already documented as a live URL. The description does not add new semantic detail about the parameter itself, so the baseline score of 3 is appropriate.

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 resource ('on-page SEO elements'), then enumerates concrete checks like title tag length, meta description, H1-H6 hierarchy, OpenGraph, and Twitter cards. This clearly distinguishes it from siblings such as seo_audit_technical and seo_audit_schema.

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 explicitly states when to use the tool ('when evaluating page-level metadata, heading structures, and social sharing previews') and provides direct exclusions with named alternatives for technical indexing and structured data validation. This leaves no ambiguity about tool selection.

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