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

The description discloses that the title is discarded after the call, but it does not state whether the operation is read-only, whether it makes network access, or what happens when a title does not exist. With no annotations present, the description carries the full transparency burden and leaves these behavioral aspects unclear.

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 brief and front-loaded with the main purpose. It contains no filler words, though the second sentence about discarding the title is somewhat redundant with the tool name and could have been replaced by parameter-related guidance.

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 nine parameters, no output schema, and no annotations, the description is far from complete. It does not explain how to supply the Wikipedia title, what the return value means, how errors are reported, or why the many schema parameters are relevant.

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 refers to a Wikipedia title, yet the schema exposes nine unrelated parameters such as ref, url, city, feed, host, json, path, zone, and query, with no title parameter at all. The individual parameter descriptions appear generic and inconsistent with the tool's stated purpose, making it impossible to map the description to the actual inputs.

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 clearly states the tool checks whether a Wikipedia title exists and notes that the title is discarded after the call. The verb 'check' and object 'Wikipedia title' are specific enough to convey the core purpose, though no context about alternatives is given.

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 provided on when to use this tool versus sibling existence-check tools such as browser-url-ok, file-path-ok, or domain-shape. There is no mention of prerequisites, limitations, or appropriate use cases.

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