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

There are no annotations, so the description carries the full burden. It does disclose that the title is 'discarded after the call,' which hints at no retention, but it says nothing about network behavior, error conditions, return value, authorization, or rate limits. The core result semantics of the check are completely absent.

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 description is only two sentences and front-loads the main verb, but the second sentence adds an opaque behavior that is not matched by the schema. The brevity is not effective because it omits the essential mapping between purpose and parameters.

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 tool with seven schema parameters, no annotations, and no output schema, this description is severely incomplete. It does not explain how to invoke the tool, what parameter carries the title, what the return value looks like, or what 'title discarded' means operationally. The agent has no reliable basis to call it correctly.

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?

Every schema property has a textual description, but none of them reference Wikipedia or a title. The description introduces a 'title' that does not exist in the schema, and the schema parameters appear to describe unrelated validation cases. An agent cannot determine which parameter—if any—holds 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 phrase 'Check whether a Wikipedia title exists' names a concrete action and resource, which is clear on its face. However, the input schema exposes seven unrelated fields (ref, url, city, feed, host, json, path) and no 'title' parameter, so the stated purpose does not connect to the actual invocation surface.

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?

No guidance is given about when to use this tool versus sibling validators such as browser-url-ok, file-path-ok, or web-fetch. It neither states the intended context nor excludes alternatives, leaving the agent to guess when wiki-title-ok is appropriate.

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