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

The description discloses that the title is discarded after the call, which is a useful data-handling trait not present in any annotations (none provided). It also implies a read-only existence check. However, it does not mention error behavior or the return format, so it is not fully transparent.

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 short sentences with the purpose stated first and the discard note second. No redundancy, filler, or unnecessary detail.

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 definition is far too sparse for an 8-parameter tool with no annotations and no output schema. It does not explain how to supply the title, what the response indicates, or how the tool relates to its many parameters. An agent cannot reliably call this tool based solely on the description.

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 schema lists 8 parameters (ref, url, city, feed, host, json, path) but none is labeled 'title' and their descriptions are generic. The tool description fails to indicate which parameter should contain the Wikipedia title, leaving the agent unable to map the tool's behavior to any schema field.

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 verb ('Check') and resource ('whether a Wikipedia title exists'), which is distinct from sibling tools like normalize-url or validate-json. Even without naming siblings, the unique focus on Wikipedia titles makes its purpose unambiguous.

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 given about when to choose this tool over alternatives, such as browser-url-ok or fetch-status. The description simply states what it does without any context, exclusions, or conditions for use.

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