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

With no annotations, the description must carry the full behavioral burden. It discloses only that the title is discarded after the call, which is useful privacy/state information, but says nothing about return behavior, error handling, network behavior, or what happens for titles that don't exist.

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?

Two front-loaded sentences with no filler: the first states the operation and the second adds a statefulness note. Every word 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?

There is no output schema, no annotations, and no parameter that can carry the title the description refers to. The agent is left without a return convention, error semantics, or even an invocable input, so the definition is not complete enough to call 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 description's central concept, the 'title', is absent from the input schema; the schema exposes only ref, url, city, feed, host, json, and path. The parameter descriptions in the schema point to entirely different concerns, so neither the description nor the schema lets an agent map a title to a usable argument.

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 specific verb and resource: checking whether a Wikipedia title exists, which distinguishes it from sibling shape/URL/JSON checkers. The purpose is easy to grasp, but it promises a 'title' input that the schema does not expose, so the purpose is only half operationalizable.

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 explicit guidance on when to invoke this tool versus alternatives such as normalize-url, validate-json, or the other shape-check siblings. The description implies the use case but gives no exclusions, prerequisites, or context about what kind of title reference is accepted.

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