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

No annotations are provided, so the description carries the full burden. The only disclosed behavior is 'Title discarded after the call,' which refers to a nonexistent parameter. There is no mention of side effects, return value, or failure behavior, making the tool's runtime behavior largely opaque.

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 extremely short (one sentence), but brevity here is under-specification rather than conciseness. It lacks critical information needed to use the tool correctly, and the mention of 'title' without a corresponding parameter is misleading.

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 nine optional parameters, no output schema, and no annotations, the description provides almost no context. It does not explain what the tool does with these inputs, which inputs are relevant, or what a successful check returns. This is severely inadequate for an agent to call the tool 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?

While the schema itself has 100% parameter description coverage, the tool description fails to connect any of the nine parameters to the stated purpose of checking a Wikipedia title. The descriptions are generic and do not explain how a caller would supply the title, so the description adds no semantic value beyond the schema and actually creates confusion.

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 action ('check whether a Wikipedia title exists'), but the input schema contains no parameter for a Wikipedia title. The parameters (ref, url, city, feed, host, json, path, zone, query) are generic and unrelated to Wikipedia titles, making the purpose unclear and not actionable.

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 provided on when to use this tool versus any of the many sibling check tools (e.g., browser-url-ok, file-path-ok, normalize-url). The description offers no context, conditions, or alternatives, leaving the agent to guess.

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