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

The description reveals one behavioral trait: the title is discarded after the call, which is useful and not present in any structured metadata. However, with no annotations present, it does not go further to clarify read-only behavior, network access, or return format, leaving much of the behavioral burden unaddressed.

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, direct sentence with no filler. The key purpose is front-loaded and the extra behavioral note about title disposal is concise, earning 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?

With a complex, seemingly generic input schema, no annotations, and no output schema, this description is far from complete. The agent cannot infer which parameter carries the Wikipedia title, what the return value looks like, or whether the operation is read-only, so the description is not sufficient for correct invocation.

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?

Despite the tool's purpose being about a Wikipedia title, no input schema property is described as a title; properties include 'ref', 'url', 'city', 'feed', 'host', 'json', and 'path' with unrelated descriptions. The description does not map the core concept to any parameter, leaving the agent unable to determine what to pass.

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 action ('Check whether a Wikipedia title exists') on a specific resource (Wikipedia title), which sufficiently distinguishes it from sibling shape-check tools. However, it does not identify which input parameter represents the title, which slightly detracts from full clarity.

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 implies that the tool should be used when an agent needs to verify the existence of a Wikipedia title. It provides no explicit when-not-to-use guidance or references to alternative tools, so the usage context is only implied rather than explicitly routed.

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