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

There are no annotations, so the description bears full responsibility for behavioral disclosure. It only states that a 'title' is discarded after the call, which is a minor detail about input handling, not about side effects, permissions, or return behavior. The description does not disclose how the tool determines existence or what it returns.

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 extremely short (one sentence), which is concise, but it is under-specified for a tool with nine parameters. It does not front-load essential information such as which parameter is the title or how to invoke it. The brevity is not effective conciseness but rather a lack of necessary content.

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?

Given the tool has nine parameters, no annotations, and no output schema, the description is grossly incomplete. An agent cannot determine how to provide the title, what constitutes a valid call, or what the response will be. The description fails to bridge the gap between its stated purpose and the actual schema.

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?

Schema description coverage is 100%, but the description adds no meaning to any parameter. It does not identify which of the nine parameters is the title to check, and the schema descriptions for each parameter are unrelated to Wikipedia (e.g., 'city' for weather, 'feed' for RSS). The disconnect makes the tool unusable without further clarification.

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 verb and resource ('Check whether a Wikipedia title exists'), but it does not indicate which parameter supplies the title. The input schema contains nine unrelated parameters (e.g., 'city', 'feed', 'host') with no 'title' field, so an agent cannot map the description to the schema. It also does not differentiate from sibling tools like 'browser-url-ok' or 'normalize-url'.

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 provided on when to use this tool versus alternatives, nor any prerequisites or conditions. The description gives no context for selecting it over the many sibling tools.

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