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

With no annotations provided, the description carries the full burden. It only discloses that the title is discarded after the call, but does not clarify whether this is a network operation, what it returns, or how it handles redirects or case variants. Some behavior is disclosed, but far too little.

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 a single, well-structured sentence that front-loads the primary purpose and adds only one relevant behavioral note. There is no wasted wording.

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?

The description is not actionable: it lacks an output schema, annotations, a parameter mapping, or any indication of the expected return value. The mismatch between the described title-checking behavior and the schema properties leaves an agent without enough information to select and invoke 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?

The description repeatedly refers to a 'title', but the input schema has no 'title' property—only ref, url, city, feed, host, json, and path. The description fails to map the core concept to any actual schema parameter, so an agent cannot determine what value to pass. The schema descriptions for the existing parameters are irrelevant to the stated purpose.

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 a specific verb ('Check'), resource ('Wikipedia title'), and predicate ('exists'), which distinguishes this tool from sibling URL, path, host, and JSON validation tools. The added note that the title is discarded reinforces its stateless purpose.

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 intended use is implied: call this when an agent needs to verify whether a Wikipedia title exists. However, it does not explicitly state when not to use it or mention alternative tools such as url-ok or browser-url-ok.

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