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

With no annotations on the tool, the description carries the full disclosure burden. The only behavioral detail is that the title is discarded after the call, which is mildly informative, but the description omits whether the check involves a network request, what the return value is, and how non-existence is signaled.

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 front-loaded with the core verb and resource, presenting no filler text. However, it is too under-specified to be considered a well-built concise description, since a key piece of information—how the title is passed—is absent.

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 has no annotations and no output schema, so the description must explain both input mapping and return semantics. It does neither: no parameter carries the title, and there is no statement about the result format or meaning. This is insufficient for correct 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 schema exposes parameters like ref, url, city, feed, host, json, and path, none of which is a Wikipedia title, while the description speaks of a title. The description fails to map the tool's central concept to any schema property, making it impossible for the agent to know which parameter supplies 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 clearly states the action ('Check whether a Wikipedia title exists') and resource (Wikipedia title), which distinguishes it at a high level from sibling validation tools. However, it does not tie the purpose to any input parameter, and the schema contains no 'title' field, leaving the agent unsure how to invoke the check.

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 implies use when title existence is in question, but it gives no explicit guidance on when to choose this tool over the many sibling shape/validation tools, no exclusions, and no mention of prerequisites. Without this, an agent has little basis for tool selection among similar validators.

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