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

No annotations are provided, so the description must carry the full burden of explaining behavior. It only says the title is discarded, but the parameters have unrelated notes like 'no disk access' and 'discarded after the length check'. It does not clarify whether a network request is made, how existence is determined, or what side effects occur.

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 structurally simple, but the brevity creates confusion rather than clarity. The mismatch between the one-line purpose and the nine unrelated parameter descriptions means the concise structure does more harm than good.

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 is no output schema, no example, and no explanation of the return value or behavior. Given the complex and contradictory input schema, the description lacks essential context about how the tool relates to Wikipedia title checking and what an agent should expect.

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 schema descriptions cover 100% of parameters, they are semantically disconnected from the stated purpose. For example, 'ref' is described as a Git ref name and 'city' as a weather hint, yet the tool is supposed to check a Wikipedia title. No parameter corresponds to the title, making the parameter semantics misleading and unusable.

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 purpose: checking whether a Wikipedia title exists. However, the actual input schema contains nine parameters (ref, url, city, feed, host, json, path, zone, query) with descriptions unrelated to Wikipedia titles, and no parameter for the title itself. This mismatch severely undermines the clarity of what the tool actually does.

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 provides no guidance on when to use this tool versus any sibling tools. It does not mention alternatives, prerequisites, or typical use cases. The conflicting parameter descriptions make it even less clear when this tool should be invoked.

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