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

No annotations are provided, so the description carries the behavioral burden. It does disclose that the title is discarded after the call, which communicates a stateless, non-retaining behavior. However, it does not mention whether the check performs a network request, what happens for missing titles, or what the return value conveys.

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, front-loaded sentences with no filler. The first states the action and target; the second adds a useful behavioral note. Every word earns its place.

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 no annotations and no output schema, the description is under-specified. It does not clarify which parameter to pass, what 'exists' means operationally, whether network access is involved, or what the response looks like. The ambiguous schema makes this lack more damaging.

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 is cluttered with many unrelated properties and even two title-like fields, while the description only says 'Title' without naming the required `wiki-title` parameter. The schema itself provides some help through the required field and property description, but the description adds no disambiguation and does not compensate for the low coverage of the large parameter list.

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 uses a specific verb ('check') and a clear resource ('whether a Wikipedia title exists'), so the tool's core purpose is immediately obvious. It also distinguishes itself from sibling tools like fetch-status and web-fetch by narrowing scope to Wikipedia title existence.

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 use this tool versus alternatives, no preconditions, and no exclusion cases. The only usage signal is implicit: use it when you need to check a Wikipedia title, but nothing differentiates it from similar-looking tools in the sibling list.

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