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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only mentions that a 'title' is discarded after the call, but this refers to a non-existent parameter. No mention of side effects, permissions, rate limits, or what happens to the actual parameters. The description is inconsistent with the schema, which is a significant transparency failure.

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 very short (two sentences), which is concise, but it is not effective because it omits essential information and introduces a misleading term. Conciseness is not valuable if the content is inaccurate or incomplete. The structure front-loads a claim that is unsupported by the schema, so it fails the purpose of concise clarity.

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?

This is a tool with 9 parameters, no required fields, and no output schema. The description must clarify what the tool does with these parameters and what it returns. It does neither. The single sentence about 'Wikipedia title' and 'discarded' is completely inadequate for an agent to understand the tool's functionality or decide when to use it. The gap between description and schema is severe.

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 has 100% description coverage, so each parameter is described individually. However, the tool description adds no meaning to any of these parameters—it references a 'title' that is not present in the schema. The description does not explain how parameters like 'url', 'json', or 'path' relate to the tool's purpose, and it actively misleads by introducing an irrelevant concept.

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 purpose ('Check whether a Wikipedia title exists'), which is clear on its face. However, it is disconnected from the actual input schema: the schema contains 9 parameters (ref, url, city, feed, host, json, path, zone, query) and none of them is a 'title'. The description introduces a concept not represented in the parameters, making the stated purpose misleading about what the tool actually operates on.

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 use this tool versus alternatives. It does not mention any context, conditions, or exclusions. The description says nothing about preferring this tool over siblings like browser-url-ok or normalize-url, nor does it clarify what kind of input it expects.

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