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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Title discarded after the call,' which is a retention hint, but it does not explain the actual behavior: how the existence check happens, what is returned, whether network access is involved, error handling, or side effects. This is severely inadequate for a tool with no annotation coverage.

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 short (one sentence), which is concise, but the conciseness is a product of under-specification. It front-loads the purpose but omits all crucial operational details. The structure is not helpful because it leaves the agent unable to map parameters to the intended action.

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?

Given the tool's complexity (9 parameters, no annotations, no output schema), the description is woefully incomplete. It does not explain which parameter carries the title, what the tool returns, any prerequisites, or how it integrates with the sibling tools. The description fails to provide an agent with the information needed 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?

The description adds no meaning beyond the schema. It does not indicate which of the nine parameters corresponds to a Wikipedia title, nor how the parameters relate to the title check. The schema descriptions are generic and mismatched (e.g., 'url' for normalize or cite, 'query' for search text), and the description fails to reconcile these with the tool's stated purpose. With 100% schema coverage but zero semantic integration, the parameter semantics are nearly useless.

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'), but the input schema contains no parameter named 'title' or any obvious mapping to one. The nine parameters (ref, url, city, feed, host, json, path, zone, query) are unrelated to Wikipedia titles, so the purpose is confused and misleading about how the tool is actually 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?

There is no guidance on when to use this tool versus siblings like browser-url-ok, domain-shape, or normalize-url. The description does not mention any context, alternatives, or exclusions, leaving the agent without criteria for selecting this tool over others.

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