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

No annotations are present, so the description carries the behavioral burden. It only says the title is 'discarded after the call,' hinting at no retention, but it does not state whether the check is read-only, whether it accesses the network, or what the result actually indicates.

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 operation, requiring only two sentences. The second sentence is somewhat tangential for invocation but does not add meaningful 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?

With seven parameters, no annotations, and no output schema, the description is far from sufficient. The missing title parameter and absent return/error semantics leave an agent unable to call the tool correctly.

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 documents seven parameters, but the description's core input, a 'title', has no corresponding schema property. The listed parameters (ref, url, city, feed, host, json, path) are all described as being discarded, so the description does not help an agent map the intended Wikipedia title to an actual argument.

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 uses a specific verb and resource ('Check whether a Wikipedia title exists'), which is clear and not tautological. However, it does not explicitly distinguish this tool from sibling shape-check tools, though the Wikipedia-title focus provides some differentiation.

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 when-to-use or when-not-to-use guidance and never names alternatives among the siblings. An agent receives no context for choosing this tool over tools like normalize-url, fetch-status, or validate-json.

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