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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions that the title is discarded after the call, which hints at data handling but leaves out network behavior, side effects, or result semantics. The discard note is also confusing because the schema has no 'title' parameter.

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 efficient at one sentence, but it under-specifies the tool to the point of being unhelpful. The single sentence omits essential operational details, so it is not appropriately sized for a tool with a complex schema.

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 seven parameters, no output schema, and no annotations, a one-sentence purpose statement is far from complete. An agent cannot determine which parameter to populate or what the check result looks like, making the tool effectively uncallable in practice.

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 schema provides descriptions for all parameters, but the tool description introduces a 'Wikipedia title' concept without mapping it to any of the seven schema parameters. This actively misleads rather than enhancing what the schema already communicates, leaving the agent unable to determine which input represents the title.

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 verb ('Check') and resource ('whether a Wikipedia title exists'), making the tool's core function understandable. It does not explicitly differentiate from sibling tools like browser-url-ok or playwright-url-ok, but the specific subject matter gives adequate clarity.

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, nor any mention of prerequisites or conditions. The one-line description provides no context about which sibling tools it complements or when an agent should select it.

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