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

The description discloses one meaningful behavioral trait: the title is discarded after the call, which is useful privacy context given there are no annotations. It does not mention whether the check involves a network request, what happens on nonexistent titles, or whether any data is stored or mutated.

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 two short sentences with the core purpose front-loaded and no filler. The second sentence adds a meaningful behavior note without extra prose.

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?

Despite being concise, the description is not complete for actual use: the caller cannot tell which parameter carries the Wikipedia title, the return value is unspecified, and the schema appears unrelated to the stated purpose. The missing parameter mapping is a critical gap.

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 parameters each have descriptions, so coverage is high, but none of the eight parameters is a 'Wikipedia title' and the description does not map the title onto any of them. This mismatch leaves an agent unable to determine what to pass as input, and the description adds no clarifying parameter semantics.

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 concrete action ('Check whether a Wikipedia title exists') on a specific resource, which distinguishes it from most sibling validation tools. However, it never defines what a valid 'title' is or how it is supplied.

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 instead of a sibling such as normalize-url, fetch-status, or validate-json. The only implied use case comes from the tool name and the one-line purpose; no exclusions or alternatives are provided.

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