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 offers one behavioral note: 'Title discarded after the call,' which is cryptic and does not clarify side effects, return values, rate limits, or error behavior. The lack of detail leaves significant uncertainty for a tool with no annotation safety net.

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 short, with two sentences, so it is concise. However, it front-loads the purpose but then adds a vague behavioral note that does not help. There is no wasted wording, but the lack of substantive content means it is not well-structured for an agent to act on. It is appropriately sized but not informative.

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 9 parameters, no required fields, no output schema, and no annotations, the description is grossly incomplete. It does not explain which parameter represents the Wikipedia title, what the return value is, how to interpret the existence check, or any operational context. An agent cannot reliably invoke this tool correctly based on the given description and schema.

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?

While the schema descriptions cover 100% of parameters, the tool's description claims to check a Wikipedia title but none of the 9 parameters (ref, url, city, feed, host, json, path, zone, query) is described as a title. The description adds no value in mapping the purpose to any parameter and actually creates confusion by not identifying which input to use. The baseline of 3 for high schema coverage is not earned because the description fails to connect the tool's action to its inputs.

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 clearly states the tool's purpose: 'Check whether a Wikipedia title exists.' It uses a specific verb and resource, and this is distinct from sibling tools like browser-url-ok or normalize-url, though it does not explicitly name alternatives. The purpose is unambiguous, but it does not connect to any specific parameter, which slightly reduces clarity.

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 on when to use this tool versus alternatives. The description gives no context about typical scenarios, prerequisites, or why an agent would choose this over a sibling. It merely states the action, leaving the agent to infer usage entirely.

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