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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, but the description adds real behavior: default filtering to safe sections and public excerpts, spoiler gating, pagination via next_offset, and the composition of clip moments (YouTube watch link at exact second, channel, on-screen check date, moment link, citation). It does not explain what 'evidence caveats' or the content hash imply, leaving a small gap.

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 core action and default behavior, then layered with spoiler, pagination, and clip details. The sentences are dense and occasionally long, but almost every clause carries information the agent needs; little is redundant.

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, the description does the heavy lifting by describing the returned content and clips in detail, and it flags the pagination mechanism. It is close to complete, missing only any hint about accepted URL forms and the meaning of max_chars for a content-heavy read.

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?

With 0% schema description coverage, the description must carry all four parameters, but it only fully explains include_spoilers and gestures at offset via the response field name 'next_offset' rather than the input name 'offset'. Neither url (accepted formats/scope) nor max_chars is addressed, so half the parameters remain undocumented.

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 states a specific verb and resource ('Retrieve a release-eligible kingy.wiki guide or section') and enumerates what comes back (source links, caveats, hash, clips). It is clear what the tool does, but it never names its siblings (search_guides, list_wikis) to help the agent disambiguate a read-by-URL from a search or listing call.

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?

It gives concrete conditional guidance: use include_spoilers=true for unclassified full bodies, solution details, and spoiler clips, otherwise only safe/public content is returned. It also adds an exclusion ('does not execute interactive calculators'). It stops short of telling the agent to use search_guides to discover a URL first, so routing among siblings stays implicit.

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