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

With no annotations provided, the description carries the behavioral disclosure burden. It does add one useful side-effect detail—'Title discarded after the call'—indicating the operation retains no state. It does not mention network behavior, return semantics, or any prerequisites, but for a simple existence check this is partial but reasonable transparency.

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 very short and front-loaded with the core purpose. The second sentence adds a behavioral note without redundancy. It loses a point because the brevity leaves important parameter mapping unexplained.

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 confusing and apparently irrelevant input schema, no output schema, and no annotations, the description is not complete enough for an agent to reliably select and invoke the tool. A single purpose sentence cannot compensate for the mismatch between the declared function and the actual parameters.

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 input schema contains seven parameters, none of which is a 'title,' despite the description claiming to check a Wikipedia title. The parameter descriptions in the schema refer to Git refs, URLs, city names, feeds, hostnames, JSON, and paths—none clearly maps to the described purpose. The description adds no clarification about which parameter should contain the title.

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 verb and resource: 'Check whether a Wikipedia title exists.' This is enough to distinguish the tool from sibling validators such as browser-url-ok or file-path-ok. However, the description never connects this purpose to any actual input property, which slightly weakens clarity.

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 about when to use this tool versus alternatives, nor any exclusions or conditions. The description implies a narrow use case, but leaves the agent to infer when the tool should be selected among the many shape-check siblings.

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