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

No annotations are present, so the description must carry full behavioral burden. It discloses only 'Title discarded after the call,' which is a minor statelessness hint, but it does not say whether the tool makes a network request, what side effects it has, or what failure modes exist.

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?

Two short sentences with no superfluous content. The primary purpose is front-loaded, and the second sentence adds useful behavioral context about the input being discarded.

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?

The tool is simple but the description omits the essential link between purpose and input schema, the return value, and the operational behavior. With no annotations and no output schema, this is insufficient for reliable invocation.

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 lists seven generic parameters (ref, url, city, feed, host, json, path), none of which is identified as a Wikipedia title. The description never maps 'Wikipedia title' to any parameter, so an agent cannot determine how to construct a valid call. This is a critical gap in parameter understanding.

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 uses the specific verb 'Check' and the resource 'Wikipedia title', so the tool's core purpose is clear and distinct from sibling validation tools. However, it does not explain how the title is supplied, and the input schema contains no 'title' parameter, making the stated purpose ambiguous in practice.

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 guidance on when to use this tool versus any sibling tool. It does not identify alternatives, prerequisites, or typical invocation contexts, leaving the agent to infer usage from the name alone.

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