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

With no annotations, the description carries the full behavioral burden. It offers only 'Title discarded after the call,' which hints at statelessness but says nothing about network calls, rate limits, authentication, failure behavior, or side effects. This is insufficient for an external-resource existence check.

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 no filler, and the main purpose is front-loaded. The second sentence is a concise behavioral guarantee, even if under-specified overall.

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 definition is far too incomplete for a tool with seven ambiguous parameters and no output schema. An agent cannot determine which parameter should contain the Wikipedia title, what the return result looks like, or how the other six parameters are used, making safe invocation nearly impossible.

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?

Though the schema properties each have descriptions, they describe unrelated concepts (Git ref, URL, city, feed, host, JSON, path) and none of them is a Wikipedia title. The description does not explain how to provide the title or how these parameters relate to the check, so the prose adds no needed 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: checking whether a Wikipedia title exists, which distinguishes it from the other shape/format validators in the sibling list. However, the clarity is reduced because the input schema contains no 'title' parameter, so the description's core noun is never connected to any input.

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 vs. alternatives such as domain-shape, github-repo-shape, or browser-url-ok. The description gives no use-case conditions, exclusions, or examples.

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