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

With no annotations present, the description carries the full burden. It adds one behavioral detail: 'Title discarded after the call,' indicating statelessness/privacy. However, it omits the return format, whether a network request occurs, and error behavior, leaving only minimal context.

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 the core purpose front-loaded. The second sentence adds a useful behavioral note, though it is redundant with the title parameter's schema description. It is appropriately concise, though not maximally informative.

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 complex, unfocused schema and the absence of annotations or output schema, the description is insufficient for reliable invocation. It fails to indicate which parameter to provide, what the tool returns, or how it behaves on failure, so an agent could easily select the wrong input among many listed.

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 lists eight heterogeneous parameters (ref, url, city, feed, host, json, path, title), most with descriptions that reference unrelated tools (e.g., 'City name for a public weather hint'). The description does not clarify that only the 'title' parameter is relevant; it merely repeats the discard note already in the schema, making parameter selection ambiguous.

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 opens with a direct, specific statement: 'Check whether a Wikipedia title exists.' This clearly identifies the verb, resource, and scope, and distinguishes it from sibling shape-check tools like file-path-ok or normalize-url by naming Wikipedia explicitly.

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 explicit when-to-use or alternative exclusions are provided. The intended use is implied by the purpose statement—use when needing to verify a Wikipedia title—but nothing names sibling alternatives or warns against misuse for other shape checks.

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