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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a useful behavioral fact—'Title discarded after the call'—indicating the input is not retained. It does not disclose return format or behavior for a nonexistent title, but it does not contradict the annotations.

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 with no filler. The purpose is front-loaded, and the second sentence earns its place by communicating a retention guarantee. It is concise without sacrificing the one behavioral caveat it chooses to make.

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?

With no output schema, the description gives no return-value information, and it fails to connect the stated purpose to any usable parameter. The mismatch between the claimed Wikipedia-title check and the actual schema fields leaves the definition operationally incomplete.

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 exposes seven unrelated parameters (ref, url, city, feed, host, json, path), none of which is a Wikipedia title, and the description never identifies which parameter should carry the title. Without that mapping, an agent cannot correctly invoke the tool despite the schema having detailed property descriptions.

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 opens with a specific verb-resource pair: 'Check whether a Wikipedia title exists.' This makes the core intent clear and distinguishes it from unrelated sibling validators. However, it never maps that purpose to any concrete parameter in the schema, so the operational purpose is only partially resolved.

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 given on when to prefer this tool over alternatives such as normalize-url, validate-json, or file-path-ok. The only usage signal is the generic existence-check statement; there are no exclusions, prerequisites, or named alternatives.

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