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

Annotations declare openWorldHint, destructiveHint, and non-idempotency, but the description adds nothing: it does not mention that this performs a live outbound fetch of the target URL, that it may be slow or rate-limited, or why a measurement operation is flagged destructive. Note a mild tension between the 'measuring quality' framing and destructiveHint=true, though the text makes no explicit read-only claim.

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 sentence with no padding and the relevant framing is front-loaded, but the sentence earns little of its place since it conveys background rather than actionable tool information. Brief, but briefness here stems from under-specification.

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?

An output schema exists so return values need no explanation, but for a single-parameter tool with many nested sub-fields and no useful annotations, the description omits the essential fact that it triggers a live Lighthouse run on one URL and returns the scored result. It is inadequate for correct selection and invocation.

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 top-level schema description coverage is 0%, so the description is expected to compensate for the single 'body' parameter, and it does not. It says nothing about required URL formatting, audits, categories, version, for_mobile, or language fields, all of which matter for calling this correctly; only the nested schema fields carry that information.

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 defines what the underlying OnPage Lighthouse API is based on, not what this tool does. It never states the action (run a live Lighthouse audit against a URL) or the output form, so an agent cannot distinguish it from siblings like get_dataforseo_on_page_lighthouse_audits or post_dataforseo_on_page_page_screenshot. It borders on restating the name rather than describing the operation.

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, no indication that this is the endpoint that actually executes a run versus the metadata endpoints (languages, versions, audits), and no exclusions. The agent must infer usage purely 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.