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

With no annotations, the description carries the full disclosure burden. It adds a useful behavioral note that the title is 'discarded after the call,' implying non-retention, but it does not clarify whether the operation is read-only, network-bound, or what output to expect. The disclosure is helpful but incomplete.

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 short sentences with no filler. The core purpose is front-loaded, and the second sentence adds a specific behavioral detail without bloat.

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 schema is unusually broad (12 optional properties) and there is no output schema or annotations. The description fails to tell the agent which parameter to supply (title, optionally lang), that other parameters can be ignored, or what the check returns. This incompleteness creates real risk of misinvocation.

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 input schema provides descriptions for all 12 parameters, including 'title: Wikipedia title to check' and 'lang: Language code for Wikipedia.' The tool description adds no further parameter meaning and does not clarify that other schema fields are likely irrelevant to this tool, so the high schema coverage sets the baseline at 3.

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 the specific action and resource: 'Check whether a Wikipedia title exists.' This clearly distinguishes the tool from siblings like browser-url-ok or fetch-status, which target URLs and HTTP statuses rather than Wikipedia titles.

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 on when to use this tool versus alternatives. There is no mention of supporting tools like web-fetch or normalize-url, no exclusion conditions, and no context such as 'use this when you only need existence, not page content.'

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