content_quality

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

With no annotations, the description carries the full burden and does substantial work: it discloses the fetch-and-extract pipeline (network egress to an arbitrary URL), the absence of auth/Google API dependency, and the scoring internals. Listing the verdicts including 'fetch_error' also surfaces the failure mode. It stops short of stating rate limits, timeouts, or behavior on paywalled/JS-rendered pages.

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?

Front-loaded with the one-line purpose, then progressively finer detail, which is good structure. The filler-phrase attribution line ('adapted from claude-seo (agricidaniel, MIT)') is provenance noise that doesn't help an agent decide or invoke, keeping this just under full marks.

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 the description needn't explain return values, yet it still volunteers the verdict enum as useful context. With only one input parameter and no annotations, the definition covers what an agent needs to invoke it correctly; only fetch-failure and timing behavior remain unaddressed.

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 0% for the single 'url' parameter, so the description must add meaning — 'Fetches the URL, extracts visible text' usefully implies this must be a live, fetchable page URL rather than an ID or path. That is helpful but thin; it gives no format hints (scheme, trailing slash, canonicalization) or whether redirects are followed.

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 verb and resource (analyse page content quality) and enumerates the exact scoring signals — thin content, filler language, information density, bigram repetition — under a stated framework (Google QRG / E-E-A-T). This is sharply distinct from siblings like content_brief, heading_audit, or page_technical_audit, so an agent can route correctly even without an explicit sibling callout.

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 (you run this on a live page to grade content quality), and the 'No Google API calls. No authentication required.' line pre-empts a common prerequisite question. However, it never states when to prefer this over content_brief or how it relates to the other audit tools, and there are no explicit exclusions or preconditions beyond the URL.

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