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

With no annotations, the description must disclose side effects, data retention, and failure modes itself; it only says 'title discarded' but no title parameter exists. It does not mention whether the check hits a live API or has rate limits.

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, but it is misleadingly terse and omits necessary context about parameter usage and return behavior. Front-loading the title check does not help when the params contradict it.

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?

There is no output schema, no annotations, and no explanation of what the tool returns (e.g., boolean, status code, error message). Given nine optional parameters and no required ones, the definition leaves the agent without enough context to call it 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?

Although schema descriptions cover 100% of parameters, they describe unrelated concepts such as Git refs, JSON validation, and timezone names. The descriptions do not explain how any parameter relates to checking a Wikipedia title, so semantic coverage is effectively zero.

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 says the tool checks whether a Wikipedia title exists, but none of the nine parameters is a title; the params are unrelated (url, city, feed, host, json, path, zone, query, ref). This mismatch makes the actual purpose very unclear.

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 browser-url-ok, fetch-status, or normalize-url. The description does not explain conditions for choosing it.

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