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

With no annotations, the description carries the full burden. It discloses that the title is discarded after the call, which is a privacy-related behavioral note. However, it does not state whether the operation is read-only, what happens on failure, or any other side effects. The discard note adds some transparency but is minimal.

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 concise (two sentences) and front-loaded with the purpose. However, it is under-specified to the point of being unhelpful; brevity is achieved at the cost of necessary detail about input and behavior.

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?

For a tool with 9 parameters and no output schema, the description is severely incomplete. It fails to explain which parameter(s) to use, the expected return value, error behavior, or any context about how the check is performed. An agent cannot reliably invoke this tool correctly with only this description.

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 has 100% coverage with descriptions for each parameter, but these descriptions are for unrelated concepts (e.g., 'Git ref name', 'HTTPS URL', 'City name'). The tool description does not bridge the gap between the stated purpose and the parameters; it never mentions which parameter to use for the Wikipedia title. Thus the description adds no value in mapping parameters to the tool's functionality.

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 purpose: 'Check whether a Wikipedia title exists.' However, it does not explain how to supply the title, and the input schema contains no parameter named 'title' — all 9 parameters refer to unrelated concepts (ref, url, city, feed, etc.). An agent would be uncertain which parameter to use, so the purpose is clear at a high level but not actionable.

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 siblings like browser-url-ok or domain-shape. No mention of prerequisites, context, or exclusions. The only hint is the name, which suggests a Wikipedia title check, but no explicit usage instructions are provided.

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