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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint; the description reinforces this with 'Safe, read-only diagnostic evaluation' and adds 'No file modifications.' This clarifies the exact operational effect beyond the schema, though it does not discuss auth or rate limits.

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 compact, front-loads the core purpose, and uses clearly labeled sections for usage and behavior. Every sentence adds actionable information without redundancy.

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 what is checked, when to use it, what not to use it for, and the target format. No output schema exists, so a brief note on expected return values would make it fully complete, but this is a minor gap.

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 fully documents the single 'target' parameter at 100% coverage as a live URL or local file path. The description does not need to add parameter detail, so it is correctly at the baseline for high schema coverage.

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 states a specific verb ('Audits') and a clear resource: on-page SEO elements, and enumerates the exact checks: title tag length/keyword placement, meta description CTR, H1 enforcement, hierarchy, OpenGraph, and Twitter cards. This distinguishes it from sibling audit tools by naming the on-page scope.

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?

Contains explicit 'Use when' guidance for page-level metadata, heading structures, and social previews, followed by two 'Do NOT use' exclusions that name alternatives (seo_audit_technical, seo_audit_schema). An agent can confidently route between siblings.

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