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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds what is inspected but says nothing about the live network fetch, timeouts, mobile emulation behavior, or repeatability cost that an agent might care about for an open-world probe.

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 dense sentence with no filler, and the primary measurement (server response time / TTFB) is front-loaded before the secondary LCP inspection. It earns its length but is slightly packed.

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 read-only, two-parameter tool with full schema coverage and no output schema, the description covers the measurement scope adequately. It still leaves gaps: no indication of relationship to sibling audit tools, no mention of whether the target must be publicly reachable, and no hint about what the markdown/json output contains.

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% with only two params, both fully documented in the schema (URL with protocol, response_format enum). The description adds no parameter-level detail beyond the schema, 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 names concrete measurements (TTFB, HTML weight, mobile LCP delay causes like lazy-loaded hero images) with a specific verb ('Measures'/'inspects'), so the agent knows exactly what this tool returns. It does not, however, contrast itself against siblings like audit_dom_bloat or audit_geo_readiness, so differentiation is left to inference from topic.

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?

Usage is implied by the description (use it when you want server response time and mobile LCP diagnostics), but there is no explicit when-to-use, when-not-to-use, or alternative-routing statement pointing at the sibling audit tools.

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