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

The only behavioral note is 'Title discarded after the call,' but since no title parameter exists, this is confusing and adds no actionable insight. With no annotations, the description fails to disclose side effects, errors, or return behavior.

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, which is concise, but it omits essential information and contains a misleading claim about a 'title' that is not in the schema. Conciseness is not a virtue when it sacrifices 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?

With 9 optional parameters, no required fields, no output schema, and a description that contradicts the schema, the definition is grossly incomplete. An agent has no idea what input to provide, what the result means, or how to distinguish this from the many similar sibling tools.

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 coverage is 100%, the tool description does not connect any parameter to its stated purpose. The parameters appear generic and unrelated to Wikipedia title checking, so the description adds no value in interpreting them.

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 clear purpose ('Check whether a Wikipedia title exists'), but the input schema exposes nine unrelated parameters (ref, url, city, feed, etc.) with no 'title' field. This mismatch makes the stated purpose unusable and misleading for an agent.

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 on when to use this tool vs siblings. The description does not mention alternatives, prerequisites, or context, and the parameter list further obscures intended use.

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