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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that the title is discarded after the call, but it does not state whether the check is read-only, whether it requires a network call, whether it returns a boolean or throws, or how optional inputs are handled.

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, each with a distinct purpose: the first states the operation and the second adds a behavioral retention note. No filler or redundancy.

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 no annotations, no output schema, nine optional parameters, and no parameter mapping, this description is not sufficient for an agent to call the tool correctly. It omits the expected return, the title mapping, and the role of the other parameters.

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%, but the description introduces a 'title' concept that does not map to any property in the schema; the schema only contains ref, url, city, feed, host, json, path, zone, and query, and additionalProperties is false. The description therefore does not help an agent identify which parameter to pass as the Wikipedia title.

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 clear, specific action: check whether a Wikipedia title exists, which directly distinguishes it from siblings like browser-url-ok and fetch-status by topic. It doesn't explicitly contrast with sibling tools, so it misses the top score.

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?

There is no guidance about when to prefer this tool over alternatives such as browser-url-ok, fetch-status, or normalize-url. The purpose wording implies a use case, but the description never says when to use it or when not to.

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