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

With no annotations at all, the description carries the full burden and does disclose real behavior: fuzzy titles are resolved through Wikipedia search, the response shape (canonical page URL, short description, thumbnail), and the paid-call requirement with exact price and chain (x402, $0.02/call, USDC, eip155:8453). It stops short of stating failure behavior for missing or disambiguation pages, which an unannotated read tool arguably still needs.

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?

The core verb+resource is front-loaded in the first clause, and the cost disclosure is correctly placed last. There is some promotional padding ('the fast, grounded way to facts') and a grammatical slip ('needs to grounded facts'), but nothing structurally wastes an agent's attention.

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 and no annotations, the description compensates by enumerating the returned fields and the resolution behavior, plus the billing model. The main gap is ambiguity/error handling for titles that match nothing or hit a disambiguation page.

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 100% for the single 'title' parameter, so baseline is 3, but the description adds genuine meaning: 'Fuzzy titles resolve via Wikipedia search' tells the agent it need not supply an exact article title. That is more than the schema's bare 'Article title or topic'.

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?

Names a specific verb and resource ('Fetch the lead summary of any English Wikipedia article') and immediately scopes it to English Wikipedia, which separates it from siblings like live_web_search, live_dictionary and dev_url_reader. The domain examples (companies, people, places, concepts) further pin down what it returns.

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 states a use condition ('Use this when an agent needs to grounded facts for any notable entity') and frames it as the 'fast, grounded' option, implying contrast with general web search. It does not name when NOT to use it or point at a specific alternative sibling, so it falls short of a 5.

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