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

No annotations are provided, so the description carries the full burden. It does disclose one behavioral trait: 'Title discarded after the call,' which indicates no retention of the title. However, it omits other important behaviors such as return value, network dependency, or error behavior.

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?

Two short sentences with no wasted words. The main purpose is front-loaded, and the discard note is a relevant behavioral detail.

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 seven schema parameters, no required fields, no output schema, and no annotations, yet the description does not explain which parameter carries the Wikipedia title or what the tool returns. An agent cannot reliably determine how to invoke this tool correctly.

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 descriptions for all parameters, so the baseline is 3, but the description introduces a 'title' concept that does not map to any schema property. It does not help an agent choose among ref, url, city, feed, host, json, or path, making the input semantics confusing rather than clarified.

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 action and resource: 'Check whether a Wikipedia title exists.' It is clear and distinguishable from sibling tools by the Wikipedia-title focus, but it does not explicitly differentiate itself from or reference any sibling tools.

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 given about when to use this tool versus alternatives such as browser-url-ok, fetch-status, or citation. The description only states what the tool does; it does not mention exclusions, prerequisites, or when-not-to-use.

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