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

The description does add one behavioral note beyond the schema: 'Title discarded after the call.' But with no annotations and no output schema, it fails to disclose return values, what 'exists' means, or how the check relates to the seven provided parameters. The missing title-input mapping leaves behavior ambiguous.

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, front-loaded, and free of filler; the first sentence states the core action and the second adds a retention note. It is concise, though the second sentence is not well connected to the schema, so efficiency slightly outpaces useful structure.

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?

The tool has seven parameters, no annotations, and no output schema, yet the description never bridges the gap between 'Wikipedia title' and the available inputs. An agent cannot determine what to pass or what result to expect, making the definition inadequate for reliable invocation.

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 describes each parameter individually, but the tool's central concept—the Wikipedia title—appears in the description while no schema property is named 'title'. The description does not explain which of ref, url, city, feed, host, json, or path should carry the title, so it creates confusion rather than adding parameter meaning.

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 specific operation and resource: 'Check whether a Wikipedia title exists.' This is distinct from sibling checker tools like file-path-ok or github-repo-shape. However, the description does not map the stated title check to any schema parameter, which weakens its practical clarity.

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?

Usage context is only implied by the phrase 'Check whether a Wikipedia title exists.' There is no explicit guidance about when to choose this tool over related validators, no prerequisites, and no conditions that would make a sibling tool more appropriate.

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