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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's real value-add is 'server HTML', which signals that client-side rendered content is not evaluated – a meaningful caveat. It says nothing about rate limits, failure modes for unreachable pages, or result format, so it adds only modest context beyond annotations.

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?

A single front-loaded sentence with the verb and scope first, followed by a checklist. The long enumeration is dense but each item defines audit scope, so little is wasted; a slightly tighter grouping would earn a 5.

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?

With no output schema, the description should convey what comes back, and the check list only roughly implies the payload – it never states whether results are pass/fail flags, extracted values, or a score, nor how unreachable or non-live pages are handled. Adequate for calling the tool, but incomplete for interpreting results.

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 all three parameters (page, store, domain) are documented in-schema, so the baseline is 3. The wording 'one live store page' loosely reinforces the page parameter but adds no format, URL-normalization, or precedence detail beyond what the schema already states.

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 names a specific verb+resource ('Check one live store page's server HTML for SEO and structured data') and enumerates the exact signals inspected, so an agent can easily distinguish a page-level HTML audit from siblings like check_page_speed or check_catalog_data. It stops short of explicitly naming a sibling it is not, which keeps it at 4 rather than 5.

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?

'one live store page' implies the per-page use case and excludes sitewide audits, but there is no explicit when-to-use guidance against check_page_speed, check_store_technical, or run_ai_readiness_check. The agent must infer routing from scope words alone.

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