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

There are no annotations, so the description carries the burden. It discloses only that the title is discarded after the call, suggesting no retention, but it says nothing about network access, side effects, errors, or output semantics for a check that presumably queries 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?

The text is short, front-loaded with the main purpose, and has no filler words. It omits essential invocation detail, but that is a completeness issue rather than a structure issue; as a concise statement it is efficient.

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?

Given the seven-parameter schema, no output schema, and no annotations, the description is severely incomplete. It does not specify the expected input, the return value, network behavior, or error conditions, so an agent cannot reliably select and call this tool.

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 seven fields (ref, url, city, feed, host, json, path), none of which is a 'title' field, and the description never names which parameter receives the Wikipedia title. This is a critical mapping failure: the description adds no meaning beyond the schema and leaves the agent unable to know how to invoke the tool correctly.

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 action ('Check whether') on a specific resource ('a Wikipedia title exists'), which is clear at a high level. It does not explicitly differentiate itself from sibling validators like domain-shape or file-path-ok, nor does it connect to the tool's actual input fields, so it is not a full 5.

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 purpose implies when to use it (when an agent needs to verify the existence of a Wikipedia title), so there is some implied guidance. However, it names no alternatives, nor does it explain when not to use it or how it compares with web-fetch or other URL shape tools.

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