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 discloses that the title is discarded after the call, but it does not clarify whether the tool is read-only, what it returns, or any side effects. The parameter descriptions in the schema mention 'discarded after the call' for several fields, but that is in the schema, not the description. The description adds minimal behavioral transparency.

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 concise (two sentences), but it is not structured to be helpful. It lacks essential information and does not front-load usage guidance. The brevity is not a virtue here because it omits critical context.

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?

Given 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. An agent has no idea how to invoke the tool correctly, which parameter to use for the title, or what to expect as a result. The tool definition is inadequate for its complexity.

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 input schema has 9 parameters, all with descriptions and 100% coverage. However, the description does not link any parameter to the Wikipedia title check. It adds no meaning beyond the schema. The schema parameters (ref, url, city, etc.) seem unrelated to the tool's stated purpose, and the description does not clarify how to specify the title. This is a significant gap.

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 action: 'Check whether a Wikipedia title exists.' This is clear and distinct from sibling tools. However, it does not indicate which parameter carries the title, and the input schema has no obvious title parameter, which could confuse an agent. Still, the purpose is stated distinctly from siblings.

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. No mention of when not to use it or what conditions apply. The description provides no context about prerequisites or intended use cases.

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