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 without description help. The description adds only that the audit concerns website speed/performance; it does not disclose latency, whether the audit hits an external live site (relevant given openWorldHint), or what the agent should supply as the target. It also does not contradict the 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?

It is a single short noun phrase with no fluff, so nothing is wasteful. But it is a bare fragment with no verb and no front-loaded operational detail, so its brevity reflects under-specification rather than efficiency.

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 an audit tool with no declared parameters, an open-ended input object, and no output schema, the description should at minimum explain how the audit target is provided, roughly what the audit returns, and how long it may take. None of that is present, leaving an agent with significant unknowns about invoking it correctly.

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 has zero declared parameters (an open object with additionalProperties=true) and 100% description coverage of that empty set, so the baseline of 4 would normally apply. However, because the input schema is a free-form object, an agent has no way to learn how the target website/URL is specified, and the description does not fill that gap, so it falls short of the baseline.

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 says it is a 'Lighthouse performance audit MCP module for website speed assessments', which conveys the general resource (website speed/performance auditing) and matches the title 'Run Lighthouse Audit'. However, the phrasing largely restates the tool name and title rather than stating a crisp verb+resource, and the actual action verb ('run') only appears in the title, not the description.

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?

There is no when-to-use guidance at all: no mention of when a performance audit is appropriate versus the sibling tools (linkchecker, provider_status, backlinks, etc.), no prerequisites, and no note about rate limits or cost of running an audit. The agent is left to infer everything from the tool name.

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