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

With no annotations at all, the description carries the full burden of explaining behavior, but it only says 'Title discarded after the call.' It omits what the tool returns, whether it performs network access, is read-only, or has error cases, and the promised title input is absent from the schema.

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; the first sentence states a purpose and the second is compact. However, the second sentence adds little useful, and the wording is concise mainly because it is under-specified.

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 optional parameters, no annotations, and no output schema, the description is far too thin. It never explains return values, how to choose any parameter, default behavior with no arguments, or whether an actual Wikipedia title can be provided under a different param name.

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 the schema descriptions already cover all 9 parameters, the description adds no meaningful parameter guidance and actually introduces a phantom 'title' concept. An agent will not know which of the nine optional string fields is the 'title,' so the description hurts rather than helps parameter selection.

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 names a concrete action ('Check whether a Wikipedia title exists') and differentiates from sibling shape-validators, but it is misleading: the input schema has no 'title' parameter and 9 unrelated string fields. With additionalProperties false, an agent cannot actually pass the Wikipedia title the description says it will check.

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 on when to use this tool, when not to use it, or which sibling tool should be selected instead. The only implied context is 'Wikipedia title existence,' but neither the schema nor the description explains how to map a title to a parameter.

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