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

With no annotations present, the description carries the full disclosure burden. It does reveal that the title is discarded after the call, which signals no retention, but it does not state whether the tool is read-only, what it returns, whether it makes a network request, or what side effects might occur.

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 concise and front-loaded, stating the operation in the first sentence and adding a brief behavioral note in the second. Every sentence is short and purposeful, though the mismatch between 'title' and the schema reduces the usefulness of that efficiency.

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 eight parameters, no output schema, and no annotations, the description is severely incomplete. It never explains how 'title' maps to any input, what the return value looks like, or which parameters are required, leaving an agent unable to invoke the tool correctly.

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 documents all listed parameters with descriptions, but the description's core noun 'title' has no corresponding property among the eight schema fields. Rather than adding meaning beyond the schema, the description introduces a parameter mismatch that makes it harder for an agent to map the intent to actual arguments.

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 verb ('Check') and resource ('whether a Wikipedia title exists'), which is distinct from sibling tools focused on URLs, file paths, or Jira keys. However, it does not explicitly differentiate itself from alternatives beyond the Wikipedia-title scope, so it stops short of a 5.

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 siblings such as web-fetch, normalize-url, or citation. The description neither provides conditions for use nor mentions exclusions or alternatives.

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