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

Says 'Title discarded after the call,' which implies no persistence, but with no annotations it does not disclose network behavior, errors, or whether the check is purely local or calls Wikipedia.

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?

Two short sentences, no filler. The entire description is front-loaded with the purpose and a side-effect note.

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?

While purpose and discard behavior are stated, the missing title parameter and lack of output/error semantics leave critical context absent, especially with nine optional inputs.

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?

The schema exposes nine unrelated optional parameters (ref, url, city, feed, host, json, path, zone, query) with descriptions copied from other tool contexts, and there is no 'title' parameter. The description does not explain how the Wikipedia title maps to any input, making invocation impossible to infer.

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 action and resource: 'Check whether a Wikipedia title exists.' This is unambiguous and distinguishes the tool from vague generic processors.

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?

The use case is implied by the purpose, but there is no explicit guidance about when to prefer this tool over sibling checkers such as browser-url-ok or file-path-ok, nor any exclusion criteria.

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