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 privacy trait beyond the schema. However, with no annotations present, the description carries the full burden for behavioral disclosure. It does not mention whether the tool makes a network request, whether it returns a boolean, or how it handles invalid or missing input, leaving some important behaviors unspecified.

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 extremely concise—two short sentences, both substantive. The purpose is stated first, and the data-handling note follows without any filler. Every word earns its place, making this an exemplary minimalist description.

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?

For a simple existence-check tool, the description is mostly sufficient, but the generic 8-parameter schema could confuse an agent about which argument is relevant. The schema fills that gap for 'query', but the lack of an output schema means the return type is only implied. Given the low complexity, this is a minor gap, hence a mid-range score.

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 input schema has 100% parameter description coverage, and one of those descriptions ('Query string for Wikipedia title lookup') directly maps to the tool's purpose. The main description adds no parameter-level information beyond what the schema already provides, so the baseline of 3 for high schema coverage is appropriate.

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 action ('Check') and a precise resource ('whether a Wikipedia title exists'), which is more specific than many sibling tools. It doesn't explicitly contrast with related validators like 'validate-json' or 'normalize-url', but the Wikipedia-title focus is enough to distinguish its core 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?

There is no indication of when to use this tool versus alternatives, no exclusions, and no mention of conditions that would favor a sibling. The description is purely declarative and leaves usage decisions entirely to inference from the tool name and sibling list.

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