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

With no annotations, the description carries the full behavioral burden and does so well: it discloses passive page loading like a visitor, no login or security testing, no storage, charge-on-success only, and a $0.50 per-call x402 price. These are exactly the side-effect, cost, and data-handling details an agent needs.

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 dense but front-loaded with the core action, and every clause appears to earn its place by covering scope, output, limitations, cost, and storage. It is a single long sentence with a closing price note, which is efficient though slightly harder to scan.

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 one-parameter audit tool with no output schema, the description is complete: it explains what the audit returns (scores, failing audits, base64 PDF), what it does not do, and the charging/storage model. Nothing critical for correct invocation appears to be missing.

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 coverage is 100%, so the single `url` parameter is already fully documented in the schema. The description adds useful scope around what URLs are acceptable (public, Shopify storefronts) and the audit context, but it does not add syntax or format details beyond the schema’s example.

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 tool action and resource: an automated Lighthouse audit of public websites or Shopify storefronts, and enumerates the exact outputs (Performance, Accessibility, Best Practices, SEO scores, failing audits, PDF report). It is immediately distinguishable from the unrelated sibling 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?

It clearly defines the target scope (public website or Shopify storefront) and exclusions (no login, no security testing), plus runtime shape (mobile emulation, single run). It does not explicitly name alternatives, but the sibling tools are unrelated, so this is strong contextual guidance.

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