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

Beyond readOnlyHint/openWorldHint, it discloses licensing (CC BY-SA), authentication requirement, absence of a free trial, no point cost, and a concrete failure mode: privacy_consent_required until the controller accepts the current privacy version. That consent gotcha is genuinely non-obvious and valuable; only the return shape is left implicit.

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?

Purpose is front-loaded, but the text is a run of fragments, and lines like "this is not a checkout" add little for this tool. The consent warning earns its place; the checkout remark does not.

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?

For a single-parameter read-only fetch with annotations covering the safety profile, the description covers auth, cost, licensing, and the consent pitfall well. Only return-shape expectations are unstated, which is acceptable with no output schema but not ideal.

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 0%, so the schema alone says only that "title" is a 1-80 char string. The description adds that it must be an article title rather than a URL and that lookups are English-only, but it never clarifies matching rules (exact title, case sensitivity, redirects).

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?

"Read one English Wikipedia summary" gives a specific verb plus resource and pins the scope to English Wikipedia, which separates it from hub_wikidata. It does not explicitly name the closest sibling, so differentiation is implied rather than stated.

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 conveys prerequisites (signed-in agent, no anonymous trial) and a negative constraint (does not accept a URL), which indirectly tells the agent to pass a title. There is no explicit when-to-use guidance versus hub_wikidata or the other hub_* lookups.

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