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

The description does disclose that the 'title' is discarded, which is a useful lifecycle detail. But because no annotations are present, the description carries the full burden: it never states whether the check is read-only, what result is returned, or how failures or invalid titles are reported. The unrelated schema-level 'discarded' notes do not clarify the tool's actual behavior.

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 core action is front-loaded. It is concise and readable, though the clarity is undermined by the mismatch between the stated purpose and the parameter list.

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 no annotations and no output schema, the description must provide enough context to invoke the tool correctly, but it fails to do so. There is no mapping from the described title check to any parameter, no return-value information, and no explanation of the seven unrelated inputs. The definition is critically incomplete for correct use.

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 contains seven parameters—ref, url, city, feed, host, json, path—none of which represents a Wikipedia title. The description mentions a title but never identifies which parameter carries it, so the agent cannot construct a correct invocation. The schema descriptions are detailed but cover the wrong domain entirely.

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 and resource: 'Check whether a Wikipedia title exists.' This clearly distinguishes the tool from URL, domain, or JSON validation siblings. However, it does not explicitly name alternatives, and the input schema exposes no 'title' parameter that would let an agent act on the stated purpose.

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 such as normalize-url or browser-url-ok, and no conditions or prerequisites are given. The description only indicates what the tool does, leaving the agent to infer applicability without support.

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