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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only notes 'Title discarded after the call,' which is a thin behavioral hint, and it is itself confusing because no parameter is named 'title.' It does not disclose what 'ok' means, what the return value is, or how the nine parameters behave.

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 brief and front-loaded with the primary purpose in the first sentence. However, the 'Title discarded after the call' sentence is questionable given that no title parameter exists, slightly weakening an otherwise efficient structure.

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?

This is a 9-parameter tool with no output schema, yet the description gives no explanation of the parameters, the meaning of the boolean result, or the tool's actual scope. The description appears mismatched with the schema (a generic validator) and is wholly inadequate for an agent to call the 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?

Although schema coverage is 100%, the description adds no meaning beyond what the schema provides — and worse, it introduces 'Wikipedia title' semantics that no parameter supports. The description fails to bridge the stated purpose to any of the actual parameters, so the agent must rely entirely on the schema's individual field descriptions.

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+resource ('Check whether a Wikipedia title exists'), but this purpose does not align with the input schema, which contains nine parameters (ref, url, city, feed, host, json, path, zone, query) — none of which is a Wikipedia title. The mismatch between the stated purpose and the actual parameters undermines clarity about what the tool truly does.

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 on when to use this tool versus siblings like browser-url-ok, fetch-status, web-fetch, or citation. Given the many similar validation/checking tools in the sibling list, an agent has no way to know which one to select without inspecting schemas.

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