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

No annotations are provided, so the description carries the disclosure burden. It does add one behavioral detail ('Title discarded after the call'), but it omits the return format, side effects, failure behavior, and why several exposed parameters are unrelated to the stated purpose. This is insufficient for a check tool with no safety annotations.

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 compact and front-loaded, stating the purpose before the discard note. Both sentences are short, though the second sentence partially duplicates information already scattered across the schema's repeated 'discarded' notes.

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 definition is critically incomplete for a title-existence check: it omits the title parameter mapping, return semantics, and any indication of what 'exists' means or what happens on failures. An agent cannot correctly invoke this tool from the provided definition.

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 does not map 'Wikipedia title' to any input schema property. The seven parameters (ref, url, city, feed, host, json, path) are all unrelated to a title, and no title parameter exists. The schema descriptions are present but do not compensate, because an agent cannot know which argument carries the title or how to invoke the check.

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 clear action and resource: 'Check whether a Wikipedia title exists.' This distinguishes the tool from the sibling shape/URL validators. However, the purpose is undermined by the input schema, which exposes no 'title' parameter, so a precise agent-facing purpose is less clear than it initially appears.

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 for when to use this tool versus siblings like validate-json, fetch-status, or other *-ok validators. The context is only implied: use it to verify a Wikipedia title. There are no explicit when-to-use, when-not-to-use, or alternative-routing instructions.

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