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

With no annotations present, the description carries the full burden of behavioral disclosure. It does add one meaningful trait: 'Title discarded after the call.' However, it does not disclose the return shape, failure behavior, or any network-related implications, so transparency is only partial.

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. The first sentence states the core action and the second adds a useful privacy/data-handling detail, so every sentence 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?

Despite a clear purpose, the overall definition is incomplete for invocation: the required domain input, 'title', is absent from the schema, and there is no output schema or annotation to clarify the return value. The agent has enough to understand what the tool conceptually does but not enough to call it 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?

The input schema contains no 'title' property; instead it lists ref, url, city, feed, host, json, and path, all described as irrelevant generic inputs. The description mentions 'Title' but never maps it to any actual parameter, so an agent cannot determine which field to populate. The existing schema descriptions do not compensate because they describe unrelated fields.

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 uses a specific verb and resource: 'Check whether a Wikipedia title exists.' This clearly distinguishes the tool from URL-checking, normalization, and other shape-check siblings in the list. The intent is immediately understandable.

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?

The description gives no guidance on when to use this tool versus alternatives such as normalize-url, browser-url-ok, or web-fetch. It includes no conditions, exclusions, or references to sibling tools, leaving the agent to infer applicability.

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