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

With no annotations, the description carries the full burden. It mentions that the title is discarded after the call, but it does not disclose side effects, network behavior, failure modes, or whether it only validates the title format or actually queries Wikipedia.

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 with the core purpose. The second sentence is cryptic and somewhat wasteful, but overall the description is concise and well structured for its length.

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 description is far from complete given the tool's complexity: there are nine parameters, no output schema, no explanation of the return value, no error semantics, and no indication which parameter should hold the title. A caller cannot reliably use this tool from the provided information.

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 does not map the notion of a 'title' to any of the nine declared parameters. The schema contains unrelated fields such as ref, url, city, feed, host, json, path, zone, and query, and additionalProperties is false, so it is unclear how a caller could pass a Wikipedia title at all.

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 a specific action and resource: 'Check whether a Wikipedia title exists.' However, it does not explain how the title is supplied, and the following sentence about discarding the title is confusing given that no title parameter exists.

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 about when to use this tool versus alternatives, no mention of applicable conditions, and no indication of what inputs should be provided. The description only states the basic function.

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