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

The only disclosed behavior, 'Title discarded after the call', is trivial and already reflected in schema descriptions for some parameters. There is no mention of side effects, authentication, rate limits, or return format. With no annotations, the description fails to convey how the tool behaves.

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 the brevity results from under-specification rather than efficiency. It omits essential information and is not front-loaded with useful context; a single misleading sentence does not earn a high score.

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 optional parameters, no output schema, and no annotations, the description is entirely inadequate. It does not explain what 'exists' means, what the return value is, or how to invoke the tool for the intended use case. Nothing an agent needs to call it correctly is present.

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?

Even though schema descriptions cover 100% of parameters, the tool description adds no meaning to them and, crucially, fails to connect any parameter to the stated 'Wikipedia title' purpose. This leaves the agent unable to map the claimed function to any input.

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 asserts 'Check whether a Wikipedia title exists', but the input schema contains no field for a title. The parameters are generic (ref, url, city, feed, host, json, path, zone, query) and none align with a Wikipedia title, so the stated purpose is misleading and does not match the actual tool interface.

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 provided on when to use this tool versus the many siblings, nor which parameter to pass for the intended 'Wikipedia title' check. An agent cannot determine the correct input from the description alone.

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