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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the title is discarded after the call, which is a minor detail, but it does not explain network access, rate limits, or the return format. This is insufficient for a tool that likely makes an external request.

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—a single sentence—but it is under-specified rather than appropriately concise. It omits critical information about parameter mapping and output, so the brevity does not serve the user.

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 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain which parameter is the title, what the response looks like, or any error conditions. An agent cannot safely or correctly invoke this tool based on the given definition.

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 description coverage is 100%, the parameter descriptions do not connect to the Wikipedia title. None of the nine parameters (ref, url, city, feed, host, json, path, zone, query) is identified as the title, so the agent cannot know which field to populate. The description adds no mapping value beyond the schema, leaving the tool effectively unusable without additional context.

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 checks whether a Wikipedia title exists, which is a specific verb+resource and differentiates it from siblings like browser-url-ok or fetch-status. However, it does not specify which input parameter corresponds to the title, which slightly muddies the purpose.

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?

The description provides no guidance on when to use this tool versus any of its 29 siblings, nor does it mention any conditions or prerequisites. An agent would have to infer usage from the name alone.

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