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

With no annotations present, the description carries the full burden of explaining side effects. It does disclose that the title is discarded, which is a useful privacy detail, but it does not state whether the operation is read-only, what happens on failure, or what the response contains. The discard note is also confusing because no title field exists in the schema.

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 text is short, front-loaded, and free of filler. The second sentence adds a behavioral note and earns its place. It is concise, though arguably too sparse for the complexity and mismatch of the schema.

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 tool with seven parameters, no annotations, no output schema, and many similar sibling tools, this description is inadequate. It fails to explain how to pass the Wikipedia title, what the return value looks like, or why the schema contains unrelated-looking fields, making correct invocation effectively impossible.

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?

Each schema property has its own description, but the tool description adds no mapping between the stated purpose and the seven parameters. None of the parameters is a Wikipedia title, and the schema descriptions for ref, url, city, feed, host, json, and path appear unrelated to the tool's purpose, so an agent cannot tell which parameter to supply.

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 and resource: 'Check whether a Wikipedia title exists.' This is specific enough to understand what the tool claims to do. However, it does not differentiate it from sibling validation tools such as browser-url-ok or normalize-url, and the input schema contains no 'title' parameter, which undercuts the clarity somewhat.

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 on when to use this tool versus alternatives, no conditions for use, and no exclusions. The sentence 'Title discarded after the call' is a behavioral note, not usage guidance.

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