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

The description says 'Title discarded after the call,' implying no persistence, but the schema has no title parameter, creating confusion about actual behavior. Without annotations, the side-effect profile is unclear.

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 a single, compact sentence with the primary function stated up front. The extra clause about the title being discarded adds minor detail but does not bloat the text.

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?

The description is far from complete for a 9-parameter tool: it does not indicate which parameter holds the title, what the response looks like, what errors may occur, or whether any parameters are actually used. The mismatch between the tool's stated purpose and its schema leaves critical context missing.

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 all 9 parameters have descriptions, those descriptions refer to unrelated concepts like Git refs, URLs, city names, RSS feeds, and JSON validation. None of them map to the stated purpose of checking a Wikipedia title, so the schema provides no usable parameter semantics.

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 clearly states the tool checks whether a Wikipedia title exists, which is a specific verb and resource. However, the input schema contains no parameter explicitly named 'title', leaving ambiguity about how to supply the title.

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 sibling tools like browser-url-ok or fetch-status. The description does not mention scenarios, prerequisites, or how this check differs from other URL/title verification tools.

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