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

The description does add one behavioral trait: the title is discarded after the call, implying a stateless, non-retaining operation. However, with no annotations present, it does not disclose return behavior, error cases, network effects, or rate limits, leaving part of the safety burden unmet.

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 two short sentences and front-loads the core purpose. The second sentence is brief, though its value is limited because 'title' does not correspond to a schema property and the discarding behavior is already echoed in the parameter descriptions.

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?

There are no annotations and no output schema, and the description omits return type, required inputs, and concrete example values. Combined with the mismatch between the stated 'title' and the actual schema properties, the definition is not sufficient 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?

The schema has seven string properties with individual descriptions, but none of them is a Wikipedia title; they describe Git refs, URLs, cities, feeds, hosts, JSON, and paths. The description's mention of a title cannot be mapped to any parameter, which is worse than silence: an agent cannot determine how to invoke this tool.

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 first sentence names the action (check existence) and resource (Wikipedia title), distinguishing it from siblings like browser-url-ok or file-path-ok. It loses a point because the description never maps 'Wikipedia title' to any actual input property, so the stated purpose is not actionable without guessing.

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 conditions, prerequisites, or when-not-to-use guidance. It does not mention alternatives such as normalize-url, web-fetch, or citation, so an agent has no basis for choosing this tool over related ones.

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