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

The description reveals a stateless behavior ('discarded after the call') and implies a boolean existence check, but it omits return values, error cases, network behavior, and output format. Since no annotations are supplied, this limited transparency is insufficient.

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 extremely brief and contains no fluff, front-loading the core action in the first sentence. It is well-structured for a simple check.

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 nine parameters, no output schema, and no parameter-level mapping to the title, the description lacks the context needed to invoke the tool correctly. It never explains how the title is supplied, what response is returned, or what 'exists' means in API terms.

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 descriptions cover all parameters, but they are semantically mismatched: ref, url, city, feed, host, json, path, zone, and query are unrelated to a Wikipedia title existence check. No parameter accepts the title to check, making the input contract unusable as described.

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 action ('Check whether a Wikipedia title exists') but does not identify which input supplies the title. With nine unrelated optional fields and no 'title' property, an agent cannot confidently map the purpose to a call.

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 prefer this tool over siblings like 'search-query-len' or 'normalize-url'. The sole behavioral note 'Title discarded after the call' does not explain use conditions or expected inputs.

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