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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: results are ordered newest first, the fields returned, and that paging is done with cursor/nextCursor. It stops short of describing rate limits, page-size behavior, or what happens when a site has no audits.

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?

Three short sentences with the resource and ordering front-loaded, then the cross-reference, then paging. The field enumeration is dense but earns its place given there is no output schema; only a minor redundancy in restating cursor/nextCursor.

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, describing the returned fields and sort order is exactly the right compensation, and the pagination hint covers the main operational concern. Missing only limit semantics and empty-result behavior for a fully complete picture.

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 67% with cursor and projectId documented in the schema; the description only restates paging via cursor and nextCursor, which the cursor field already explains. It adds the scoping idea ('a site's SEO Audits') but says nothing about limit bounds or defaults, so it is roughly at the baseline for partially documented parameters.

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?

States a specific verb (lists) and resource (a site's SEO Audits), and even enumerates the returned fields (runId, start time, trigger type, audited URL), which sharpens the identity of the resource. It clearly distinguishes itself from get_audit by pointing to that tool for single-record reads.

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?

Explicitly routes single-audit reads to get_audit, which is the key alternative among the sibling tools. It does not state exclusions such as when not to list or which sibling handles findings/pages within an audit, so it falls short of full when/when-not coverage.

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