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

With no annotations present, the description should carry the full behavioral disclosure. The only behavioral detail provided is that the title is 'discarded after the call,' which is a privacy note, but it omits whether the tool makes network requests, whether it is read-only, what it returns, or how failures surface. The phrase 'Title discarded' also conflicts with the lack of a title parameter, causing ambiguity.

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 and front-loaded, which earns points. But it fails to earn its place by not explaining the essential mechanics needed for invocation. Given the massive mismatch between title and the actual schema, this brevity is under-informativeness rather than clean conciseness, deserving a middle score.

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 nine optional parameters, no output schema, no annotations, and an ambiguous title-schema mapping, the description is critically incomplete. There is no explanation of how to pass a Wikipedia title, what type of return to expect, or which parameter is required/suitable for the intended operation. This tool is unusable without additional context.

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 the input schema provides 100% parameter descriptions, the tool description adds no semantic meaning that connects the parameters to a Wikipedia title check. The claimed 'title' is not present in the schema, and the description does not explain how any of the nine parameters relate to the action. This is a significant gap beyond the structured schema, so the baseline of 3 is reduced.

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: checking whether a Wikipedia title exists. However, there is no 'title' parameter in the input schema, and the provided parameters (ref, url, city, feed, host, json, path, zone, query) do not obviously map to a Wikipedia title. This creates a clear mismatch between what the description says the tool does and how it can be invoked.

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 gives no guidance on when to use this tool versus alternatives. There is no mention of conditions favoring this tool, no exclusions, and no comparisons to siblings such as browser-url-ok or file-path-ok. The presence of 'ok' style sibling tools further emphasizes the need for usage differentiation, which is completely absent.

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