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

There are no annotations, so the description carries the behavioral burden. It does disclose that the title is discarded after the call, suggesting no retention or persistent side effects. However, it does not state whether the check is read-only, whether it makes a network request, or what happens on failure, leaving important behavior unspecified.

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 primary purpose. The second sentence about discarding the title contributes some behavioral information without unnecessary verbosity. It earns its place, though the overall definition is incomplete for other reasons.

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 mismatch between the described behavior and the actual schema, the definition is not complete enough for correct invocation. It lacks any guidance on which parameter holds the Wikipedia title, what the return value looks like, and any network or error behavior. The presence of many unrelated schema properties makes this gap more severe.

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 refers to a 'title', but the input schema has no title parameter at all. The provided parameters are ref, url, city, feed, host, json, and path, none of which is clearly mapped to the Wikipedia-title check. An agent cannot determine which argument to pass, making the description fundamentally inadequate for parameter semantics.

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 verb and resource: check whether a Wikipedia title exists. This distinguishes it from sibling tools like browser-url-ok or file-path-ok, which target other domains. However, the phrase 'Title discarded after the call' adds an unusual secondary behavior that slightly distracts from the core purpose.

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 on when to use this tool instead of a sibling such as citation, normalize-url, or web-fetch. The intended use is only implied by the purpose statement, with no exclusions, prerequisites, or alternative-routing guidance.

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