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

The description adds one behavioral trait beyond the purpose: 'Title discarded after the call,' which signals that the input is not retained. However, with no annotations present, it does not disclose return behavior, network dependencies, or other side effects, so the transparency is only partial.

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 two sentences with no wasted words. The primary purpose is front-loaded, and the second sentence provides a distinct behavioral note. It is concise and well structured for a simple checker tool.

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 no output schema and no annotations, the description is too thin. It fails to explain how the Wikipedia title should be supplied, which parameter to use, or what the tool returns. The mismatch between the description and the input schema leaves an agent with insufficient information to invoke the tool reliably.

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?

Although the schema properties each have descriptions, the tool description refers to a 'title' parameter that does not appear anywhere in the schema. The schema exposes ref, url, city, feed, host, json, and path, but none is clearly mapped to the Wikipedia title being checked. This mismatch undermines parameter clarity despite high schema description coverage.

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 the operation: 'Check whether a Wikipedia title exists.' This is a specific verb and resource, and the tool name reinforces the purpose. It does not explicitly distinguish itself from sibling tools, but the core purpose is unambiguous.

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?

The description gives no explicit guidance about when to use this tool versus alternatives, and mentions no exclusions or prerequisites. It only states the basic action, leaving the agent to infer the use case without additional context.

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