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

The only behavioral note is that a title is discarded after the call, but the input schema exposes no `title` property. With no annotations provided, this minimal statement does not adequately disclose behavior such as return values, network effects, or side effects.

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 and front-loaded, but it is underspecified for a tool with nine optional parameters and no output schema. The second sentence is a behavioral note about a nonexistent title parameter, so not every sentence clearly earns its place.

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?

Given nine optional params, no required params, no annotations, and no output schema, the description is operationally incomplete. An agent cannot tell which parameter supplies the title, what the tool returns, or how to interpret success or failure.

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?

Although all nine schema parameters have descriptions, the tool description does not connect any of them to the stated purpose of checking a Wikipedia title. The mention of 'title' refers to a concept absent from the schema, so the description adds confusion rather than meaningful 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 clearly states the action and resource: checking whether a Wikipedia title exists. It is distinct from sibling check tools like browser-url-ok or file-path-ok, but the clarity is undercut because no `title` parameter exists in the input schema.

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 over alternatives, what inputs are relevant, or what conditions should trigger its use. Given the large set of sibling check/shape tools, the routing context is missing.

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