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

The description does disclose that the input title is discarded after the call, which suggests a stateless, non-persistent check. However, with no annotations, it does not disclose return behavior, error behavior, network usage, or whether this is a live Wikipedia lookup.

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 short and front-loaded, stating the key purpose in the first sentence. The second sentence adds a statelessness hint, though it is somewhat ambiguous given the missing title parameter.

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 not complete enough to invoke correctly: the main input parameter is absent from the schema, there are no annotations, no output schema, and no explanation of results or edge cases. The description alone leaves critical gaps.

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 description mentions a 'title' but the input schema has no title parameter; instead it lists unrelated fields like ref, url, city, feed, host, json, and path. No schema description or tool description explains which parameter carries the Wikipedia title, making the tool effectively uncallable from the provided documentation.

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 clearly distinguishes it from sibling tools like validate-json or normalize-url, even though it doesn't name them explicitly.

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 on when to use this tool versus alternatives such as web-fetch or fetch-status. The only implied usage is checking Wikipedia title existence, but no context, prerequisites, or exclusions are provided.

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