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

The only behavioral note, 'Title discarded after the call,' references a non-existent 'title' parameter and adds no useful context. With no annotations provided, the description carries the full burden of describing side effects, permissions, or return behavior, but it offers none beyond this vague and irrelevant discard statement.

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 sentence, which is concise, but it is underspecified and misleading. It fails to communicate the tool's actual functionality or how to use its parameters, making the brevity a liability rather than a strength.

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?

For a tool with nine parameters, no output schema, and no annotations, the description is grossly inadequate. It leaves the agent unable to determine what input to provide, what the tool returns, or how it differs from sibling validators, making it impossible to use 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?

Though the schema descriptions cover all parameters, they are generic ('Git ref name', 'HTTPS URL', etc.) and repeatedly state 'discarded after the check.' The description does not explain how any of these nine parameters relate to checking a Wikipedia title, so it provides no added semantic value and actually conflicts with the stated purpose.

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') but the input schema contains no title parameter—only generic fields like ref, url, city, and feed. This mismatch makes the actual purpose ambiguous and misleading, as the agent cannot determine which parameter corresponds to the Wikipedia 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 the many sibling check tools (browser-url-ok, fetch-status, etc.). The description does not specify the intended input type, context, or any conditions that would favor this tool over alternatives.

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