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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the bar is lower. The description still adds meaningful context beyond them: no network fetching, no generated summary, free/no-key/no-credits during validation, and that source and input limits apply. The only weakness is that 'bounded text budget' and 'limits apply' are left vague.

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?

Core purpose is front-loaded well, but two of the five sentences are promotional/pricing filler ('FREE during validation', 'No key, credits, wallet or preparation needed') and 'Existing source and input limits apply' is vague padding. The description is short overall but not every sentence earns its place.

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 needn't be documented, and annotations cover the safety profile. The description supplies the key behavioral facts (no fetch, no summary, constraint on text size). The main residual gap is the ambiguous 'Supply your task in input' instruction for a nested object with 0% schema description coverage.

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%, so the description carries the full burden. It gestures at the parameters conceptually ('Wikipedia article HTML' for html, 'sections' for section, 'bounded text budget' for maxChars, 'source links' for sourceUrl), but gives no syntax, default, or bounds information. 'Supply your task in input' is actively confusing since input is an html/sourceUrl object, not a task.

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 (pack) and resource (supplied Wikipedia article HTML) and enumerates what the pack contains: sections, source links, attribution, bounded text. The explicit 'No fetching or generated summary' distinguishes it from sibling fetchers like web_wikipedia_read. It doesn't directly name the sibling pack_preview or web_page_pack, so sibling differentiation is inferential rather than explicit.

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?

'No fetching or generated summary' implies the caller must already hold the HTML, which channels usage toward a fetch-then-pack flow, and 'FREE during validation' hints at availability constraints. But no alternative tool is named for the fetch step and there is no explicit when-to-use statement. Usage is implied rather than stated.

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