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

No annotations are provided, so the description carries the full burden. It adds one behavioral note—'Title discarded after the call'—but omits that this likely performs an external Wikipedia request, whether any side effects or rate limits apply, and what the result contains.

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, front-loaded, and contains no filler; both sentences earn their place. However, it is under-specified, so compactness does not make up for missing input mapping and behavioral details.

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?

For a tool with seven schema parameters and no output schema, this description is not complete enough to invoke correctly. The essential title-to-parameter mapping and the result/return behavior are absent.

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 exposes seven parameters (ref, url, city, feed, host, json, path), yet none is described as conveying a Wikipedia title. The description mentions a title but never maps it to a parameter, so an agent cannot know which input to provide.

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 specific action and resource: 'Check whether a Wikipedia title exists.' This is clear enough about the tool's purpose, but it does not differentiate it from sibling lookup/validation tools such as normalize-url or web-fetch.

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?

There is no guidance about when to choose this tool over alternatives, no exclusions, and no conditions. The only signal is the implied use case of verifying Wikipedia title existence, which is not enough to route an agent reliably.

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