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

With no annotations, the description carries the full burden. It discloses that 'Title discarded after the call', but this is confusing because no 'title' parameter exists. It also doesn't mention whether the operation is read-only, makes network calls, or has side effects, which is a significant gap for a check-like tool.

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 concise (two short sentences), but it omits essential information about how to supply the title. While it is not verbose, it is under-specified to the point of being nearly useless for correct invocation.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description is grossly inadequate. It provides no indication of required parameters, expected output, error conditions, or how to formulate a valid request. The mismatch between the described purpose and the actual schema makes it impossible for an agent to use this 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?

Although schema description coverage is 100%, the parameter descriptions are generic and unrelated to the tool's stated purpose. The tool description adds no mapping between its purpose and any of the 9 parameters, so it fails to explain which parameter represents the Wikipedia title. This is a critical omission.

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 clear purpose: check if a Wikipedia title exists. However, it does not specify which input parameter carries the title, and the schema lists unrelated parameters (ref, url, city, feed, etc.), creating confusion about how the tool is actually invoked. It also doesn't differentiate from sibling tools like 'browser-url-ok' or 'domain-shape'.

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 alternatives. The description does not mention any conditions, exclusions, or comparison to sibling tools, leaving the agent to guess the appropriate context.

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