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

No annotations are present, so the description must carry the transparency burden. It only says the title is discarded after the call, but does not disclose whether a network request happens, whether it is strictly read-only, or what happens when a title does not exist. Minor transparency is provided, but insufficient for an unannotated tool.

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 short and front-loaded, with no redundant wording. The discard note is an extra behavior hint, but the brevity comes at the cost of missing necessary parameter and usage details.

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?

With 9 optional parameters, no output schema, no annotations, and no mapping of which parameter carries the title, the description is drastically under-specified. An agent cannot determine how to satisfy the tool's stated purpose.

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?

While schema coverage is 100%, the description is completely disconnected from the schema parameters. Nine fields are listed, none named 'title' or obviously mapped to Wikipedia title existence, and the description adds no meaning to help choose the correct parameter.

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 operation ('check whether a Wikipedia title exists') on a distinct resource, helping distinguish it from sibling shape/url checkers. The wording is direct rather than a tautology, though the schema does not expose a title parameter which slightly undermines callability.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives such as web-fetch or browser-url-ok, nor does it state under which conditions to choose this tool over a sibling.

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