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

The description adds the useful behavioral detail that the title is 'discarded after the call,' implying no retention or side effects. However, with no annotations, it does not disclose the return value, error behavior, or whether existence is checked exactly or as a prefix.

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 are front-loaded with the primary purpose: 'Check whether a Wikipedia title exists.' The additional 'Title discarded after the call' is a relevant detail with no wasted words.

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 not complete enough to call reliably: there is no output schema, no guidance on what the tool returns, and the schema has seven string parameters that appear unrelated to the described Wikipedia-title check. An agent cannot determine which parameter carries the title or what a successful check looks like.

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 introduces a conceptual 'title' input, but the input schema contains no 'title' parameter or any parameter clearly representing a Wikipedia title. Instead it lists unrelated parameters like ref, url, city, feed, host, json, and path, making it impossible for an agent to map the intended argument to the schema.

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 specific verb and resource: 'Check whether a Wikipedia title exists.' This clearly distinguishes it from sibling URL, fetch, and validation tools by naming Wikipedia titles as the target. The purpose is unambiguous even though the schema does not match.

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 guidance about when to use this tool versus alternatives such as normalizing a URL, fetching a page, or validating other shapes. The description only says what the tool does, not when it should be preferred or avoided.

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